| 3 | Approval of the Agenda | |
|---|---|---|
| R3-201500 | RAN3#107-Bis-e Meeting Agenda | Chairman (Ericsson) |
| 4 | Approval of the minutes from previous meetings | |
| R3-201501 | RAN3#107-e Meeting Report | ETSI - MCC |
| 5 | Documents for immediate consideration | |
| R3-201627 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-201629 | List of E-mail Discussions | Chairman (Ericsson) |
| R3-202548 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| R3-202552 | List of E-mail Discussions | Chairman (Ericsson) |
| 7.2 | Port Assignment Request for W1 Interface - Coordination with IANA | |
| R3-201679 | On port number allocation for W1 and other RAN3 interfaces | Intel Corporation |
| R3-202044 | Discussion on LS on port allocation | Huawei |
| R3-202045 | [DRAFT] LS on port allocation | Huawei |
| R3-202553 | LS on port allocation | Huawei |
| 8.1 | New Incoming LSs | |
| R3-201502 | Reply LS on general status of work | 3GPP CT1, Ericsson |
| R3-201503 | Reply LS on extended NAS timers for CE in 5GS | 3GPP CT1, Ericsson |
| R3-201504 | Reply LS on Rel-16 NB-IoT enhancements | 3GPP CT1, Ericsson |
| R3-201505 | Reply LS on sending CAG ID | 3GPP CT1, Ericsson |
| R3-201506 | Reply LS on Mobile-terminated Early Data Transmission | 3GPP CT1, Ericsson |
| R3-201507 | Reply LS on Further clarifications on GLI/GCI and Line ID/ HFC_Identifier | 3GPP CT4, Nokia |
| R3-201508 | LS on updated Rel-16 LTE and NR parameter lists | 3GPP RAN1, qualcomm |
| R3-201509 | Reply LS on CAG definition | 3GPP RAN2, Huawei |
| R3-201510 | LS on TDD pattern exchange for NR-DC power control | 3GPP RAN2, Vivo |
| R3-201511 | LS on avoiding simultaneous CHO and CPC | 3GPP RAN2, Nokia |
| R3-201512 | Reply LS on Rel-16 NB-IoT enhancements | 3GPP RAN2, Huawei |
| R3-201513 | LS on RACS and signaling of UE capabilities at handover | 3GPP RAN2, Ericsson |
| R3-201514 | LS on Additional path reporting with uplink timing measurements | 3GPP RAN2, Ericsson |
| R3-201515 | Reply LS on Information Needed for MRO in UE RLF Report | 3GPP RAN2, CATT |
| R3-201516 | LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | 3GPP RAN2, Nokia |
| R3-201517 | LS on gNB measurements report mapping for NR Positioning | 3GPP RAN4, Ericsson |
| R3-201518 | LS on enhancing location information reporting with Dual Connectivity | 3GPP SA2, Nokia |
| R3-201519 | Reply LS on analytics support for energy saving | 3GPP SA5, Orange |
| R3-201520 | LS on the status update of the SON support for NR works | 3GPP SA5, Intel |
| R3-201707 | Discussion on TDD pattern for NR-DC power control coordination | ZTE, vivo |
| R3-201708 | CR38.423 on TDD pattern for NR-DC power control cordination for sol1 | ZTE, vivo |
| R3-201709 | CR38.473 on TDD pattern for NR-DC power control cordination for sol1 | ZTE, vivo |
| R3-201718 | CR38423 on TDD pattern signaling for NR-DC power coordination for sol2 | vivo, ZTE |
| R3-201719 | CR38473 on TDD pattern signaling for NR-DC power coordination for sol2 | vivo, ZTE |
| R3-201720 | Draft] LS Reply on TDD pattern exchange for NR-DC power control | vivo, ZTE |
| R3-202207 | Discussion on handover without SN configuration query | Huawei |
| R3-202208 | Provision of used DRB IDs | Huawei |
| R3-202209 | Provision of used DRB IDs | Huawei |
| R3-202210 | Provision of used DRB IDs | Huawei |
| R3-202211 | Provision of used DRB IDs | Huawei |
| R3-202212 | Provision of used DRB IDs | Huawei |
| R3-202213 | Provision of used DRB IDs | Huawei |
| R3-202214 | Provision of used DRB IDs | Huawei |
| R3-202215 | Provision of used DRB IDs | Huawei |
| R3-202216 | [DRAFT] Reply LS on handover without SN configuration query | Huawei |
| R3-202217 | Discussion on NR-DC Power Control | Huawei |
| R3-202218 | Support of NR-DC Power Control | Huawei |
| R3-202219 | Support of NR-DC Power Control | Huawei |
| R3-202220 | [DRAFT] Reply LS on TDD pattern exchange for NR-DC power control | Huawei |
| R3-202358 | LS on Generic Slice Template with Public Safety Feedback | TCCA |
| R3-202554 | Summary of offline discussion on TDD pattern exchange for NR-DC power control | ZTE |
| R3-202555 | CR38.423 on TDD pattern for NR-DC power control cordination for sol1 | ZTE, vivo, Ericsson |
| R3-202556 | CR38.473 on TDD pattern for NR-DC power control cordination for sol1 | ZTE, vivo, Ericsson |
| R3-202557 | Reply LS on TDD pattern exchange for NR-DC power control | vivo, ZTE |
| R3-202560 | Summary of offline discussion on handover without SN configuration query | Huawei |
| R3-202627 | Reply to: LS on the status update of the SON support for NR works | CMCC |
| R3-202630 | Reply LS on the status update of the SON support for NR works | CMCC |
| 8.2 | LSin received during the meeting | |
| R3-202710 | Response LS on SRS and SSB configuration for NR Positioning | RAN2 |
| R3-202711 | Reply LS on Rel-16 NB-IoT enhancements | RAN2 |
| R3-202712 | LS on NR SCG release for power saving | RAN2 |
| 8.3 | Left over LSs / pending actions | |
| R3-201521 | LS on UE identifier for UP CIoT 5GS Optimisation | 3GPP RAN2, LGE |
| R3-201522 | Reply LS on assistance indication for WUS | 3GPP RAN2, Qualcomm |
| R3-201523 | Reply LS on assistance indication for WUS | 3GPP SA2, Huawei |
| R3-201524 | LS on 5GC assisted cell selection for accessing network slice | 3GPP SA2, ZTE |
| R3-201525 | Reply LS on assistance indication for WUS | 3GPP SA2, Huawei |
| R3-201526 | Reply on radio resource management policy | 3GPP SA5, Ericsson |
| R3-201527 | LS on analysis of GSMA GST attributes | 3GPP SA5, China Mobile |
| R3-202016 | [DRAFT] Response LS on the “LS OUT on Location of UEs and associated key issues” | THALES |
| R3-202456 | Response to R3-202207 – R3-202215 | Ericsson |
| R3-202457 | Response to R3-202216 | Ericsson |
| R3-202558 | Response to 5GC assisted cell selection for accessing network slice | current meeting |
| R3-202559 | Reply to: LS on analysis of GSMA GST attributes | current meeting |
| R3-202561 | Reply LS on handover without SN configuration query | Huawei |
| R3-202563 | [DRAFT] Response LS on the “LS OUT on Location of UEs and associated key issues” | THALES |
| R3-202824 | Response LS on the “LS out on Location of UEs and associated key issues” | THALES |
| R3-202832 | Reply LS on handover without SN configuration query | Huawei |
| 8.3.2 | CSI-RS Configuration Transfer | |
| R3-201622 | Discussion on CSI-RS Configuration Transfer over X2/Xn | China Telecom, Ericsson, Huawei, ZTE, CATT |
| R3-201852 | Introduction of CSI-RS configuration switch on Xn | Huawei |
| R3-201853 | Introduction of CSI-RS configuration switch on X2 | Huawei |
| R3-202184 | Signalling of Neighbour CSI-RS relation structure between NG-RAN nodes | Ericsson |
| R3-202185 | Neighbour CSI-RS configuration status indication over Xn | Ericsson |
| R3-202186 | Neighbour CSI-RS configuration status indication over X2 | Ericsson |
| R3-202562 | Summary of offline discussion on CSI-RS Configuration Transfer | China Telecom |
| R3-202725 | Introduction of CSI-RS configuration switch on Xn | Huawei, China Telecom |
| R3-202726 | Introduction of CSI-RS configuration switch on X2 | Huawei |
| 9.2.1 | Rel-15 WUS | |
| R3-201711 | Consideration on CN awareness of WUS | Huawei |
| R3-201712 | CN awareness of WUS | Huawei |
| R3-201713 | [Draft]Reply LS on assistance indication for WUS from SA2 | Huawei |
| R3-201729 | Consideration on WUS awareness in Rel-15 | ZTE, Ericsson |
| R3-201730 | [Draft]Reply LS on WUS | ZTE, Ericsson |
| R3-201809 | On improving the efficiency of WUS in release 15 | Qualcomm Incorporated |
| R3-201810 | [DRAFT] Further reply LS on assistance indication for WUS | Qualcomm Incorporated |
| R3-202166 | Correction of WUS paging | Nokia, Nokia Shanghai Bell |
| R3-202167 | Correction of WUS paging | Nokia, Nokia Shanghai Bell |
| R3-202168 | Correction of WUS paging | Nokia, Nokia Shanghai Bell |
| R3-202564 | Summary of offline discussion on Rel-15 WUS | ZTE |
| R3-202626 | [Draft]Reply LS on WUS | ZTE, Ericsson |
| 9.2.2 | Others | |
| R3-202021 | Remove the “EPC Forbidden” from the Core Network Type Restrictions | Ericsson |
| R3-202023 | Remove the “EPC Forbidden” from the Core Network Type Restrictions | Ericsson |
| R3-202097 | On the removal of the “EPC Forbidden” from the Core Network Type Restrictions in S1AP | Ericsson |
| R3-202428 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| R3-202429 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| R3-202566 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| R3-202567 | Correction the NCC for 5G to 4G handover | Nokia, Nokia Shanghai Bell |
| 9.3.1 | RAN Sharing | |
| R3-201843 | Further discussion on Global Cell Identities and Global NG-RAN Node Identities in network sharing scenarios | Nokia, Nokia Shanghai Bell |
| R3-201844 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-201845 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-201895 | Further discussion on RAN sharing | ZTE Corporation |
| R3-201897 | Clarification on RAN node identification with network sharing scenario | ZTE Corporation |
| R3-201899 | Clarification on RAN node identification with network sharing scenario | ZTE Corporation |
| R3-201900 | Clarification on RAN node identification with network sharing scenario | ZTE Corporation |
| R3-201903 | Clarification on RAN node identification with network sharing scenario | ZTE Corporation |
| R3-202098 | Correction for Network Sharing - MOCN | Ericsson |
| R3-202099 | Correction for Network Sharing - MOCN | Ericsson |
| R3-202100 | Correction for Network Sharing - MOCN | Ericsson |
| R3-202101 | Correction for Network Sharing - MOCN | Ericsson |
| R3-202102 | On RAN Sharing – 5GS and EN-DC | Ericsson |
| R3-202419 | Further discussions on NCGI and TAI when multiple cell IDs are broadcast in SIB1 | Huawei |
| R3-202568 | Summary of offline discussion on RAN sharing | Huawei |
| R3-202722 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-202723 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-202798 | Summary of offline discussion on RAN sharing | Huawei |
| R3-202799 | Clarification on Network Identities for RAN Sharing | Huawei |
| R3-202802 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-202803 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-202862 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| R3-202863 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | Nokia, Nokia Shanghai Bell |
| 9.3.2 | Removal of Last PDU Session | |
| R3-201750 | Correction of removal of last PDU session | Nokia, Nokia Shanghai Bell, Orange |
| R3-201751 | Correction of removal of last PDU session | Nokia, Nokia Shanghai Bell, Orange |
| R3-201752 | Correction of removal of last PDU session | Nokia, Nokia Shanghai Bell, Orange |
| R3-201960 | Further discussion on last PDU session release | Huawei |
| R3-201961 | Further discussion on last PDU session release | Huawei |
| R3-202103 | Discussions on the removal of the last PDU Session | Ericsson |
| R3-202455 | On release of the last PDU Session | Qualcomm Incorporated |
| 9.3.3 | DC Operation Mode | |
| R3-201753 | Correction of SN-only node | Nokia, Nokia Shanghai Bell, Orange |
| R3-201754 | Correction of SN-only node | Nokia, Nokia Shanghai Bell, Orange |
| R3-201755 | Correction of SN-only node | Nokia, Nokia Shanghai Bell, Orange |
| R3-201978 | Discussion on NSA mode indication over XnAP | CATT,China Telecom,ZTE |
| R3-201979 | Correction on NSA mode indication | CATT,China Telecom,ZTE |
| R3-201980 | Correction on NSA mode indication (Rel-16) | CATT,China Telecom,ZTE |
| R3-202104 | PSCell/SCell-only operation mode | Ericsson |
| R3-202105 | Support of PSCell/SCell-only operation mode | Ericsson |
| R3-202106 | Support of PSCell/SCell-only operation mode | Ericsson |
| R3-202107 | Support of PSCell/SCell-only operation mode | Ericsson |
| R3-202108 | Support of PSCell/SCell-only operation mode | Ericsson |
| R3-202109 | Support of PSCell/SCell-only operation mode | Ericsson |
| R3-202110 | Support of PSCell/SCell-only operation mode | Ericsson |
| R3-202569 | summary of offline discussion on DC Operation mode | Ericsson |
| 9.3.4 | SgNB Initiated SgNB Modification | |
| R3-201973 | Discussion on nested SN modification procedure | CATT |
| R3-201974 | Correction on nested SN modification procedure for MR-DC | CATT |
| R3-201975 | Correction on nested SN modification procedure for MR-DC | CATT |
| R3-201976 | Correction on nested SN modification procedure for EN-DC | CATT |
| R3-201977 | Correction on nested SN modification procedure for EN-DC | CATT |
| R3-202221 | Potential issue during modification procedure | Huawei, China Telecom, China Unicom |
| R3-202222 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-202223 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-202224 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-202225 | Introduction of transaction ID during modification procedure | Huawei, China Telecom, China Unicom |
| R3-202570 | Summary of offline discussion on SgNBinit_SgNBmod | CATT |
| R3-202736 | Correction on nested SN modification procedure | CATT |
| R3-202737 | Correction on nested SN modification procedure for EN-DC | CATT |
| R3-202786 | Summary of offline discussion on SgNBinit_SgNBmod | CATT |
| 9.3.5 | E-RAB ID in Modification Procedure | |
| R3-201756 | Correction of revoke E-RAB ID | Nokia, Nokia Shanghai Bell |
| R3-201757 | Correction of revoke E-RAB ID | Nokia, Nokia Shanghai Bell |
| R3-201758 | Correction of revoke E-RAB ID | Nokia, Nokia Shanghai Bell |
| R3-201962 | E-RAB ID revocation in modification procedure | Huawei |
| R3-201963 | E-RAB ID revocation in modification procedure | Huawei |
| R3-201964 | E-RAB ID revocation in modification procedure | Huawei |
| R3-202024 | Handling the IE in the modification messages | Ericsson, ZTE |
| R3-202026 | Handling the IE in the modification messages | Ericsson, ZTE |
| R3-202111 | Discussions on handling E-RAB ID in Modification Procedure | Ericsson |
| R3-202585 | Summary of offline discussion on E-RAB ID in Modification Procedure | Ericsson (Moderator) |
| R3-202667 | Correction of revoke E-RAB ID | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-202668 | Correction of revoke E-RAB ID | Nokia, Nokia Shanghai Bell, Ericsson |
| 9.3.6 | AS Re-Keying Handling | |
| R3-201981 | Discussion on AS rekeying handling | CATT,China Telecom |
| R3-201982 | Correction on AS rekeying handling | CATT,China Telecom |
| R3-201983 | Correction on AS rekeying handling (Rel-16) | CATT,China Telecom |
| R3-201984 | [Draft]LS on AS rekeying handling | CATT |
| R3-202028 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-202029 | Clarification of AS re-keying in the UE Context Modification procedure | Ericsson |
| R3-202112 | AS re-keying and Emergency Fallback in the UE Context Modification procedure | Ericsson |
| R3-202586 | Summary of offline discussion on AS Re-Keying Handling | CATT |
| R3-202738 | Correction on AS rekeying handling | CATT, China Telecom |
| R3-202739 | Correction on AS rekeying handling | CATT, China Telecom |
| R3-202740 | [Draft]LS on AS rekeying handling | CATT |
| R3-202833 | LS on AS rekeying handling | CATT |
| 9.3.8 | Others | |
| R3-201623 | Further Discussion on the semantics description of 5GS TAC and Served PLMNs | China Telecom, ZTE, CATT ,Huawei |
| R3-201624 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT ,Huawei |
| R3-201625 | Update on semantics description of 5GS TAC and Served PLMN | China Telecom, ZTE, CATT, Huawei |
| R3-202411 | Further discussions on IE cellreservedforoperator | Huawei, China Telecom, China Unicom |
| R3-202412 | Clarification to 36.423 on broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-202413 | Clarification to 36.423 on broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-202414 | Clarification to 38.423 on broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| R3-202415 | Clarification to 38.423 on broadcast PLMN list under RAN sharing case | Huawei, China Telecom, China Unicom |
| 9.3.8.1 | Other Corrections | |
| R3-201692 | Corrections for PWS Cancel | Nokia, Nokia Shanghai Bell |
| R3-201693 | Corrections for PWS Cancel | Nokia, Nokia Shanghai Bell |
| R3-201846 | Correction of connected en-gNBs | Nokia, Nokia Shanghai Bell |
| R3-201847 | Correction of connected en-gNBs | Nokia, Nokia Shanghai Bell |
| R3-201848 | Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-201849 | Corrected handling of Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-201850 | Corrected handling of Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-201854 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201855 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201856 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201857 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201858 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201859 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201860 | Encoding PLMNs in served cell information NR | Huawei |
| R3-201896 | Correction for usage of Cell Broadcast Cancelled List | Nokia, Nokia Shanghai Bell |
| R3-201901 | Correction for usage of Cell Broadcast Cancelled List | Nokia, Nokia Shanghai Bell |
| R3-201908 | Update on semantics description of 5GS TAC and Served PLMN | ZTE Corporation, China Telecom, CATT |
| R3-201909 | Discussion on Measurement Gap Deactivation | Nokia, Nokia Shanghai Bell |
| R3-201910 | Update on semantics description of 5GS TAC and Served PLMN | ZTE Corporation, China Telecom, CATT |
| R3-201911 | Correction on UE CONTEXT MODIFICATION REQUIRED message | ZTE, Samsung, China Telecom |
| R3-201912 | Measurement Gap Deactivation | Nokia, Nokia Shanghai Bell |
| R3-201913 | Correction on UE CONTEXT MODIFICATION REQUIRED message | ZTE Corporation, Samsung, China Telecom |
| R3-201915 | Measurement Gap Deactivation | Nokia, Nokia Shanghai Bell |
| R3-201916 | Discussion on DL UP TNL Information to be setup list over F1 | ZTE Corporation, China Telecom, China Unicom |
| R3-201917 | R15_Correction on DL UP TNL Information to be setup list for TS38.473 (Option 1) | ZTE Corporation, China Telecom, China Unicom |
| R3-201918 | R15_Correction on DL UP TNL Information to be setup list for TS38.473 (Option 2) | ZTE Corporation, China Telecom, China Unicom |
| R3-201919 | R16_Correction on DL UP TNL Information to be setup list for TS38.473 (Option 1) | ZTE Corporation, China Telecom, China Unicom |
| R3-201920 | R16_Correction on DL UP TNL Information to be setup list for TS38.473 (Option 2) | ZTE Corporation, China Telecom, China Unicom |
| R3-201965 | Further discussion on NAS Non-Delivery | Huawei |
| R3-201966 | Further discussion on NAS Non-Delivery | Huawei |
| R3-201985 | Discussion on Location report | CATT |
| R3-201986 | Correction on location report | CATT |
| R3-201987 | Correction on location report | CATT |
| R3-201988 | Correction on UE context modifciation procedure | CATT |
| R3-201989 | Correction on UE context modifciation procedure | CATT |
| R3-202031 | RRC Reconfiguration in DU initiated UE Context Modification Required CR 38.473 | Ericsson |
| R3-202033 | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | Ericsson |
| R3-202035 | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | Ericsson |
| R3-202113 | Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-202114 | Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-202115 | RRC Reconfiguration in DU initiated UE Context Modification Required CR 38.473 | Ericsson |
| R3-202116 | RRC Reconfiguration in DU initiated UE Context Modification Required | Ericsson |
| R3-202117 | Adding the missing supportfor for AS Rekeying during handover | Ericsson |
| R3-202118 | Adding the missing supportfor for AS Rekeying during handover | Ericsson |
| R3-202119 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-202120 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-202274 | CR 36.423 Correction to E-UTRA-NR Cell-level Resource Coordination | Ericsson, Deutsche Telekom |
| R3-202421 | CR38.423 for Correction on SN release request | ZTE |
| R3-202422 | CR38.423 for Correction on SN release request | ZTE |
| R3-202423 | CR36.423 for Correction on SN release request | ZTE |
| R3-202443 | Handling re-mapped QoS flow over F1 and E1 interface | Samsung |
| R3-202444 | Correction relating the re-mapped QoS flow for the UL data forwarding during HO | Samsung |
| R3-202445 | Correction relating the re-mapped QoS flow for the UL data forwarding during HO | Samsung |
| R3-202446 | Correction of the DRB release after QoS flow re-mapping and the Old QoS Flow List update during HO | Samsung |
| R3-202447 | Correction of the DRB release after QoS flow re-mapping and the Old QoS Flow List update during HO | Samsung |
| R3-202448 | Correction of the DRB release after QoS flow re-mapping | Samsung |
| R3-202449 | Correction of the DRB release after QoS flow re-mapping | Samsung |
| R3-202450 | Correction relating the re-mapped QoS flow for the UL data forwarding during HO | Samsung |
| R3-202451 | Correction relating the re-mapped QoS flow for the UL data forwarding during HO | Samsung |
| R3-202453 | CR36.423 for Correction on SN release request | ZTE |
| R3-202454 | CR36.423 for Correction on SN release request | ZTE |
| R3-202587 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-202588 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-202589 | Corrections for PWS Cancel | Nokia, Nokia Shanghai Bell |
| R3-202590 | Corrections for PWS Cancel | Nokia, Nokia Shanghai Bell |
| R3-202591 | Summary of offline discussion on Corrections for PWS Cancel | Nokia |
| R3-202592 | Summary of offline discussion on Correction of connected en-gNBs | Nokia |
| R3-202593 | Correction of connected en-gNBs | Nokia, Nokia Shanghai Bell |
| R3-202594 | Correction of connected en-gNBs | Nokia, Nokia Shanghai Bell |
| R3-202595 | Corrected handling of Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-202596 | Corrected handling of Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-202598 | Encoding PLMNs in served cell information NR - Semantics clarifications | Huawei, Ericsson |
| R3-202599 | Encoding PLMNs in served cell information NR | Huawei, Ericsson |
| R3-202600 | Encoding PLMNs in served cell information NR | Huawei, Ericsson |
| R3-202601 | Encoding PLMNs in served cell information NR | Huawei, Ericsson |
| R3-202602 | Encoding PLMNs in served cell information NR | Huawei, Ericsson |
| R3-202603 | Encoding PLMNs in served cell information NR | Huawei, Ericsson |
| R3-202604 | Correction for usage of Cell Broadcast Cancelled List | Nokia, Nokia Shanghai Bell |
| R3-202605 | Correction for usage of Cell Broadcast Cancelled List | Nokia, Nokia Shanghai Bell |
| R3-202606 | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | Ericsson |
| R3-202607 | Clarification the usage of the New AMF UE NGAP ID included in the UE CONTEXT MODIFICATION REQUEST message | Ericsson |
| R3-202608 | Summary of offline discussion on RRC Reconfiguration in DU initiated UE Context Modification Required | Ericsson |
| R3-202609 | Summary of offline discussion on Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-202610 | Summary of offline discussion on Adding the missing supportfor for AS Rekeying during handover | Ericsson |
| R3-202611 | Summary of offline discussion on re-mapped QoS flow | samsung |
| R3-202612 | Summary of offline discussion on RB release after QoS flow re-mapping | samsung |
| R3-202628 | Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-202629 | Selected PLMN ID in INITIAL UE MESSAGE for untrusted non-3GPP access | Ericsson |
| R3-202684 | Correction of the Old QoS Flow List update during HO | Samsung, Ericsson |
| R3-202685 | Correction of the DRB release after QoS flow re-mapping and the Old QoS Flow List update during HO | Samsung |
| R3-202687 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-202688 | Correction to PDU SESSION RESOURCE MODIFY CONFIRM | Ericsson |
| R3-202695 | Summary of offline discussion on Location report | CATT - Moderator |
| R3-202696 | Summary of offline dsicussion on Correction on SN release request | ZTE - Moderator |
| R3-202741 | Correction on location report | CATT |
| R3-202742 | Correction on location report | CATT |
| R3-202764 | CR38.423 for Correction on SN release request | ZTE |
| R3-202765 | CR38.423 for Correction on SN release request | ZTE |
| R3-202766 | CR36.423 for Correction on SN release request | ZTE |
| R3-202767 | CR36.423 for Correction on SN release request | ZTE |
| R3-202779 | Summary of offline discussion on RRC Reconfiguration in DU initiated UE Context Modification Required | Ericsson |
| R3-202792 | Summary of offline discussion on Location report | CATT - Moderator |
| R3-202804 | Corrected handling of Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-202805 | Corrected handling of Selected TAI for TNL discovery for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-202806 | Encoding PLMNs in served cell information NR | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-202807 | Encoding PLMNs in served cell information NR | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-202808 | Encoding PLMNs in served cell information NR | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-202809 | Encoding PLMNs in served cell information NR | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-202810 | Encoding PLMNs in served cell information NR | Huawei, Ericsson , Nokia, Nokia Shanghai Bell, ZTE |
| R3-202811 | Encoding PLMNs in served cell information NR | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-202812 | Encoding PLMNs in served cell information IEs - semantics corrections | Huawei, Ericsson, ZTE |
| R3-202813 | Encoding PLMNs in served cell information IEs - semantics corrections | Huawei, Ericsson, ZTE |
| R3-202814 | Encoding PLMNs in served cell information IEs - semantics corrections | Huawei, Ericsson, ZTE |
| R3-202815 | Encoding PLMNs in served cell information IEs - semantics corrections | Huawei, Ericsson, ZTE |
| R3-202816 | Encoding PLMNs in served cell information IEs - semantics corrections | Huawei, Ericsson, ZTE |
| R3-202817 | Encoding PLMNs in served cell information IEs - semantics corrections | Huawei, Ericsson, ZTE |
| 9.3.8.2 | Pure Stage-2 Corrections | |
| R3-201811 | Correction of gNB behaviour during mobility in RRC_INACTIVE | Qualcomm Incorporated |
| R3-202036 | Corrections to Stage 2 ANR description | Ericsson |
| R3-202038 | Corrections to Stage 2 ANR description | Ericsson |
| R3-202226 | Clarification on the SN initiated SN change procedure | Huawei, China Telecom, China Unicom |
| R3-202227 | Clarification on the SN initiated SN change procedure | Huawei, China Telecom, China Unicom |
| R3-202303 | Correction for gNB-DU transmission stop descriptoin in the inter-gNB HO involving gNB-CU-UP change | Intel Corporation, CATT |
| R3-202304 | Correction for gNB-DU transmission stop descriptoin in the inter-gNB HO involving gNB-CU-UP change | Intel Corporation, CATT |
| R3-202763 | Summary of offline discussion on gNB-DU TX stop | Intel - Moderator |
| R3-202822 | Correction for gNB-DU transmission stop descriptoin in the inter-gNB HO involving gNB-CU-UP change | Intel Corporation, CATT, Nokia, Nokia Shanghai Bell |
| R3-202823 | Correction for gNB-DU transmission stop descriptoin in the inter-gNB HO involving gNB-CU-UP change | Intel Corporation, CATT, Nokia, Nokia Shanghai Bell |
| 10.1 | General | |
| R3-201528 | Addition of SON feature | Huawei |
| R3-201555 | BLCR to 38.420: Addition of MDT feature | CMCC |
| R3-201556 | BLCR to 38.420: Addition of SON feature | CMCC |
| R3-201557 | BLCR to 38.470: Addition of SON feature | CMCC |
| R3-201558 | BLCR to 38.460: Addition of SON feature | CMCC |
| R3-201566 | MDT support for EN-DC | Huawei |
| R3-201569 | Addition of RACH Optimization Feature | CMCC, Huawei |
| R3-201574 | MDT support for EN-DC | Huawei, SAMSUNG |
| R3-201608 | Addition of SON features | Huawei |
| R3-201609 | Addition of SON feature | CATT |
| R3-201610 | Addition of SON features | CMCC, Huawei |
| R3-201611 | Addition of MDT features | Samsung |
| R3-201612 | Addition of SON features | Huawei |
| R3-201613 | Addition of MDT feature | Huawei |
| R3-201614 | Addition of SON features | Samsung |
| R3-201615 | MDT Configuration support for XnAP | Ericsson |
| R3-201616 | Addition of SON features | Ericsson |
| R3-201617 | Addition of MDT features | ZTE |
| R3-201618 | Addition of SON features | Huawei |
| R3-201619 | Addition of MDT features | Samsung |
| R3-202436 | Updated work plan for SON and MDT WI | China Mobile International Ltd |
| R3-202461 | CB: # 1000_Email_SON-MDT_BLs | CMCC - Moderator |
| R3-202617 | MDT support for EN-DC | Huawei, SAMSUNG |
| R3-202761 | LS on Logged MDT Status | Ericsson |
| R3-202869 | LS on Logged MDT Status | Ericsson |
| R3-202914 | Addition of SON feature | Huawei |
| R3-202915 | Addition of SON feature | CATT |
| R3-202916 | Addition of SON features | CMCC, Huawei |
| R3-202917 | Addition of SON features | Huawei |
| R3-202918 | Addition of SON features | Samsung |
| R3-202919 | Addition of SON features | Huawei |
| R3-202920 | Addition of MDT features | Samsung |
| R3-202921 | MDT Configuration support for XnAP | Ericsson |
| 10.2.1.1 | Intra-System and Inter-System Connection Failure | |
| R3-201735 | (TP for SON BL CR for TS 38.413): Intra-System and Inter-System Connection Failure | Huawei |
| R3-201736 | (TP for SON BL CR for TS 38.423): Intra-System and Inter-System Connection Failure | Huawei |
| R3-201737 | (TP for SON BL CR for TS 38.300): Intra-System and Inter-System Connection Failure | Huawei |
| R3-201929 | Discussion on support of intra-system and inter-system MRO | CATT,CMCC |
| R3-201930 | [Draft]LS to RAN2 on support of MRO | CATT |
| R3-201931 | Discussion on tranfer of RAReport and ConnEstFailReport | CATT |
| R3-201932 | (TP on SON BLCR for 38.413)Addition of RAReport and ConnEstFailReport transfer | CATT |
| R3-201933 | (TP on SON BLCR for 38.423)Addition of RAReport and ConnEstFailReport transfer | CATT |
| R3-202069 | (TP for SON BL CR for TS 38.423) Intra-System and Inter-System Connection Failure for MRO | Samsung |
| R3-202070 | (TP for SON BL CR for TS 38.413) Intra-System and Inter-System Connection Failure for MRO | Samsung |
| R3-202071 | (TP for SON BL CR for TS 38.300) Intra-System and Inter-System Connection Failure for MRO | Samsung |
| R3-202072 | LS on information needed for MRO in UE RLF Report | Samsung |
| R3-202391 | TP for [NR_SON_MDT] BL CR for TS 38.300) Introduction of RLF report | ZTE |
| R3-202392 | Left open issue for intra system and inter system MRO | ZTE |
| R3-202393 | Re-connected Cell ID for intra system inter RAT MRO | ZTE |
| R3-202435 | TP to SON BLCR 38.300 on MRO corrections | China Mobile International Ltd |
| R3-202462 | CB: # 1001_Email_SON-MDT_ConnFail | Samsung - Moderator |
| R3-202632 | CB: # 1001_Email_SON-MDT_ConnFail | Samsung - Moderator |
| R3-202690 | (TP for SON BL CR for TS 38.413): Intra-System and Inter-System Connection Failure | Huawei |
| R3-202699 | (TP for SON BL CR for TS 38.423) Intra-System and Inter-System Connection Failure for MRO | Samsung |
| R3-202700 | (TP for SON BL CR for TS 38.300) Intra-System and Inter-System Connection Failure for MRO | Samsung |
| R3-202701 | LS on information needed for MRO in UE RLF Report | Samsung |
| R3-202818 | LS on information needed for MRO in UE RLF Report | Samsung |
| R3-202819 | (TP for SON BL CR for TS 38.300) Intra-System and Inter-System Connection Failure for MRO | Samsung |
| R3-202838 | (TP for SON BL CR for TS 38.413): Intra-System and Inter-System Connection Failure | Huawei |
| 10.2.1.2 | Inter-System Ping-Pong and Unnecessary Handover | |
| R3-201738 | (TP for SON BL CR for TS 38.300): Inter-System Ping-Pong and Unnecessary Handover | Huawei |
| R3-201739 | (TP for SON BL CR for TS 38.423): Inter-System Ping-Pong and Unnecessary Handover | Huawei |
| R3-201934 | (TP for SON BL CR for TS 38.413)Correction on inter-system unnecessary HO | CATT |
| R3-202463 | CB: # 1002_Email_SON-MDT_PingPong | CATT - Moderator |
| R3-202631 | (TP for SON BL CR for TS 38.413)Correction on inter-system unnecessary HO | CATT |
| R3-202743 | (TP for SON BL CR for TS 38.413)Correction on inter-system unnecessary HO | CATT |
| 10.2.1.4 | CU-DU Aspects for MRO | |
| R3-201791 | Remaining issues in CU-DU MRO | Qualcomm Incorporated |
| R3-202121 | Signalling of RLF information from gNB-CU to gNB-DU | Ericsson |
| R3-202122 | Signalling of RLF information from gNB-DU to gNB-CU | Ericsson |
| R3-202123 | Addition of SON features TP 38.470 | Ericsson |
| R3-202124 | Signalling of RLF Report to gNB-DU TP 38.473 | Ericsson |
| R3-202125 | Handling of RLF in the gNB-DU TP 38.473 | Ericsson |
| R3-202126 | Addition of SON features CR 38.401 | Ericsson |
| R3-202317 | Open issues for CU-DU MRO | LG Electronics |
| R3-202318 | (TP for NR_SON_MDT BL CR for TS 38.473): Open issues for CU-DU MRO | LG Electronics |
| R3-202394 | Left issue for CU-DU MRO | ZTE |
| R3-202395 | TP for [NR_SON_MDT] BL CR for TS 38.473) CU-DU MRO | ZTE |
| R3-202464 | CB: # 1003_Email_SON-MDT_CUDUMRO | LG - Moderator |
| R3-202633 | CB: # 1003_Email_SON-MDT_CUDUMRO | LG - Moderator |
| 10.2.1.6 | UE Reported Mobility History | |
| R3-201740 | (TP for SON BL CR for TS 38.413) UE reported history information | Huawei |
| R3-201741 | (TP for SON BL CR for TS 38.423) UE reported history information | Huawei |
| R3-202465 | CB: # 1004_Email_SON-MDT_MobHist | Huawei - Moderator |
| R3-202634 | CB: # 1004_Email_SON-MDT_MobHist | Huawei - Moderator |
| 10.2.2.1 | MLB for Xn/X2/F1/E1 | |
| R3-201742 | (TP for SON BL CR for TS 38.423): MLB | Huawei |
| R3-201743 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-201744 | (TP for SON BL CR for TS 36.423): MLB | Huawei |
| R3-201745 | (TP for SON BL CR for TS 38.463): MLB | Huawei |
| R3-201832 | Load reporting metric per slice for improved interoperability | Nokia, Nokia Shanghai Bell |
| R3-201833 | Clarifications and handling of open points on load reporting metric | Nokia, Nokia Shanghai Bell |
| R3-201834 | (TP for SON BL CR for TS 38.423) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-201835 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-201836 | (TP for SON BL CR for TS 38.473) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-201837 | (TP for SON BL CR for TS 36.423) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-201894 | Further consideration on active UEs (updated) | NTT DOCOMO, INC., Verizon Wireless, Deutsche Telekom, Vodafone, TELECOM ITALIA, CMCC |
| R3-201898 | (TP for SON BL CR on 36.423) Addition of active UEs in load reporting | NTT DOCOMO INC. |
| R3-201902 | (TP for SON BL CR on 38.423) Addition of active UEs in load reporting | NTT DOCOMO INC. |
| R3-201906 | (TP for SON BL CR on 38.473) Addition of active UEs in load reporting | NTT DOCOMO INC. |
| R3-201995 | Introduction of MLB for EN-DC | CATT |
| R3-201996 | Remaining Issues for MLB metrics | CATT |
| R3-201997 | (TP on SON BLCR for 38.423) TP on MLB metrics | CATT |
| R3-201998 | (TP on SON BLCR for 38.473) TP on MLB metrics | CATT |
| R3-201999 | (TP on SON BLCR for 36.423) TP on MLB metrics | CATT |
| R3-202267 | MLB – TP for BL CR for 38.423 | Ericsson |
| R3-202268 | MLB – TP for BL CR for 38.473 | Ericsson |
| R3-202269 | MLB – TP for BL CR for 38.463 | Ericsson |
| R3-202270 | MLB – TP to BL CR for 36.423 | Ericsson |
| R3-202271 | MLB – TP to BL CR for 38.300 | Ericsson |
| R3-202272 | Discussion on remaining FFS for MLB in Rel-16 | Ericsson |
| R3-202273 | Discussion on TNL and HW capacity indicators for MLB in Rel-16 | Ericsson |
| R3-202396 | Left Issues for MLB | ZTE |
| R3-202397 | TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of MLB Features | ZTE |
| R3-202398 | TP for [NR_SON_MDT] BL CR for TS 38.423) Addition of MLB Features | ZTE |
| R3-202399 | TP for [NR_SON_MDT] BL CR for TS 38.473) Addition of MLB Features | ZTE |
| R3-202438 | TP to SON BLCR 38.300 on support of MLB | China Mobile International Ltd |
| R3-202439 | Remaining issues of MLB | CMCC |
| R3-202440 | TP to SON BLCR 38.300 on support of MLB | CMCC |
| R3-202441 | TP to SON BLCR 38.423 on support of MLB | CMCC |
| R3-202466 | CB: # 1005_Email_SON-MDT__MLB | Nokia - Moderator |
| R3-202549 | TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of MLB Features | ZTE |
| R3-202550 | TP for [NR_SON_MDT] BL CR for TS 38.423) Addition of MLB Features | ZTE |
| R3-202551 | TP for [NR_SON_MDT] BL CR for TS 38.473) Addition of MLB Features | ZTE |
| R3-202635 | CB: # 1005_Email_SON-MDT__MLB | Nokia - Moderator |
| R3-202689 | (TP for SON BL CR for TS 38.473): MLB | Huawei |
| R3-202744 | (TP on SON BLCR for 36.423) TP on MLB metrics | CATT |
| R3-202746 | (TP for SON BL CR for TS 38.463) Load reporting updates | Nokia, Nokia Shanghai Bell |
| R3-202781 | TP to SON BLCR 38.300 on support of MLB | CMCC |
| R3-202797 | MLB – TP for BL CR for 38.423 | Ericsson |
| R3-202825 | TP to SON BLCR 38.300 on support of MLB | CMCC |
| R3-202837 | Introduction of MLB for EN-DC | CATT |
| R3-202840 | CB: # 1005_Email_SON-MDT__MLB | Nokia - Moderator |
| R3-202864 | MLB – TP for BL CR for 38.423 | Ericsson |
| R3-202865 | (TP to BL CR 36.300): Introduction of MLB for EN-DC | CATT |
| 10.2.3.1 | RACH Optimization Enhancements | |
| R3-201626 | Discussion on the Leftover Issues on PRACH Optimization | China Telecom |
| R3-201628 | (TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of PRACH Coordination in EN-DC | China Telecom,CATT |
| R3-201792 | Finalize PRACH parameters to be exchanged over Xn and F1 for RACH optimization | Qualcomm Incorporated |
| R3-201839 | Discussion on PRACH Configuration Exchange based on CB#29 at RAN3#107-e | Nokia, Nokia Shanghai Bell |
| R3-201861 | (TP for SON BL CR for TS 38.473): PRACH configuration exchange over (resubmission of R3-201347) | Huawei, CATT, CMCC |
| R3-201862 | (TP for SON BL CR for TS 38.423): PRACH configuration exchange | Huawei |
| R3-201863 | (TP for SON BL CR for TS 38.473): PRACH configuration exchange | Huawei |
| R3-201864 | (TP for SON BL CR for TS 38.423):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-201865 | (TP for SON BL CR for TS 38.473):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-201990 | (TP for SON BL CR for TS 38.423): Resubmission of R3-201319(outcome of offline discussion in last meeting) | CATT,China Telecom,CMCC,Huawei |
| R3-201991 | Discussion on PRACH coordination | CATT |
| R3-201992 | (TP on SON BLCR for 38.300) TP on PRACH coordination | CATT |
| R3-201993 | (TP on SON BLCR for 38.423) TP on PRACH coordination | CATT |
| R3-201994 | (TP on SON BLCR for 38.473) TP on PRACH coordination | CATT |
| R3-202263 | TP for RACH Report Signalling on F1 Interface | Ericsson |
| R3-202264 | TP for RACH Report Signalling on XN Interface | Ericsson |
| R3-202265 | TP for PRACH Configuration IE Signalling on Xn Interface | Ericsson |
| R3-202266 | Solution for RACH Conflict Detection and Resolution at gNB-DU | Ericsson |
| R3-202400 | Left issue for PRACH configuraiton parameter | ZTE |
| R3-202467 | CB: # 1006_Email_SON-MDT_PRACHConfig | CATT - Moderator |
| R3-202636 | CB: # 1006_Email_SON-MDT_PRACHConfig | CATT - Moderator |
| R3-202733 | (TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of PRACH Coordination in EN-DC | China Telecom,CATT |
| R3-202745 | (TP for SON BL CR for TS 38.423): Resubmission of R3-201319(outcome of offline discussion in last meeting) | CATT,China Telecom,CMCC,Huawei |
| R3-202782 | (TP for SON BL CR for TS 38.473): PRACH configuration exchange over (resubmission of R3-201347) | Huawei, CATT, CMCC |
| R3-202783 | (TP for SON BL CR for TS 38.423):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-202784 | (TP for SON BL CR for TS 38.473):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-202820 | (TP for [NR_SON_MDT] BL CR for TS 36.423) Addition of PRACH Coordination in EN-DC | China Telecom,CATT |
| R3-202821 | (TP for SON BL CR for TS 38.423): Resubmission of R3-201319(outcome of offline discussion in last meeting) | CATT,China Telecom,CMCC,Huawei |
| R3-202827 | (TP for SON BL CR for TS 38.473): PRACH configuration exchange over (resubmission of R3-201347) | Huawei, CATT, CMCC |
| R3-202828 | (TP for SON BL CR for TS 38.423):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-202829 | (TP for SON BL CR for TS 38.473):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-202866 | (TP for SON BL CR for TS 38.423):UE RACH report for RACH optimization | Huawei, China Telecom |
| R3-202867 | (TP for SON BL CR for TS 38.473):UE RACH report for RACH optimization | Huawei, China Telecom |
| 10.2.3.2 | Configuration Conflicts for RACH Optimization | |
| R3-201793 | RACH configuration conflict detection and resolution function | Qualcomm Incorporated |
| R3-201840 | Discussion on PRACH Configuration Conflict Resolution based on CB#30 at RAN3#107-e | Nokia, Nokia Shanghai Bell |
| R3-202286 | (TP for SON BL CR for TS 38.423) RACH configuration conflict detection and resolution function | Qualcomm Incorporated |
| R3-202287 | (TP for SON BL CR for TS 38.473) RACH configuration conflict detection and resolution function | Qualcomm Incorporated |
| R3-202401 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Left issue for RACH Report from UE | ZTE |
| R3-202402 | (TP for [NR_SON_MDT] BL CR for TS 38.423)Addition of PRACH exchange | ZTE |
| R3-202403 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Addition of PRACH exchange | ZTE |
| R3-202468 | CB: # 1007_Email_SON-MDT_RACHReport | Qualcomm - Moderator |
| R3-202637 | CB: # 1007_Email_SON-MDT_RACHReport | Qualcomm - Moderator |
| 10.3.1 | MDT Activation and Reporting | |
| R3-201783 | (TP for MDT BL CR for TS 38.423) Remaining issues in MDT | Qualcomm Incorporated |
| R3-201784 | (TP for MDT BL CR for TS 38.413) Remaining Issues in MDT | Qualcomm Incorporated |
| R3-201790 | Remaining issues in MDT | Qualcomm Incorporated |
| R3-201838 | (TP for MDT BL CR for TS 38.473) Further discussion on addition of immediate MDT for intra-DU inter-cell mobility scenarios | Nokia, Nokia Shanghai Bell |
| R3-201841 | (TP for SON BL CR for TS 38.473) Introduction of RACH Assistance Information | Nokia, Nokia Shanghai Bell |
| R3-201842 | (TP for SON BL CR for TS 38.423) Introduction of RACH Assistance Information | Nokia, Nokia Shanghai Bell |
| R3-201866 | (TP for MDT BL CR for TS 38.413): Clean up FFSes in MDT BLCR | Huawei,CMCC |
| R3-201867 | (TP for MDT BL CR for TS 38.423): Clean up FFSes in MDT BLCR | Huawei, CMCC |
| R3-201868 | (TP for MDT BL CR for TS 38.473): Clean up FFSes in MDT BLCR | Huawei |
| R3-201869 | (TP for MDT BL CR for TS 38.463): Clean up FFSes in MDT BLCR | Huawei |
| R3-201870 | Beam related configuration for immediate MDT | Huawei |
| R3-201871 | (TP for MDT BL CR for TS 38.413): Beam related configuration for immediate MDT | Huawei |
| R3-201872 | (TP for MDT BL CR for TS 38.423): Beam related configuration for immediate MDT | Huawei |
| R3-202000 | Support of MDT | CATT |
| R3-202001 | (TP on MDT BLCR for 38.413)Correction on MDT | CATT |
| R3-202002 | (TP on MDT BLCR for 38.423)Correction on MDT | CATT |
| R3-202258 | TP for introducing Area scope for neighbour cell configuration on NGAP | Ericsson |
| R3-202259 | TP for introducing Area scope for neighbour cell configuration on Xn | Ericsson |
| R3-202305 | URI for Streaming Trace reporting | Nokia, Nokia Shanghai Bell |
| R3-202319 | Open issues for MDT activation and report | LG Electronics |
| R3-202379 | (TP for MDT BL CR for 38.473) Correction for Cell Traffic Trace message and MDT configuration | Samsung R&D Institute UK |
| R3-202380 | (TP for MDT BL CR for 38.463) Correction for Cell Traffic Trace message and MDT configuration | Samsung R&D Institute UK |
| R3-202381 | (TP for MDT BL CR for 38.413) Addition of Privacy Indicator to Cell Traffic Trace message | Samsung R&D Institute UK |
| R3-202382 | (TP for MDT BL for 38.423) Propagation for Management Based MDT PLMN List | Samsung R&D Institute UK |
| R3-202404 | Left issue for MDT | ZTE |
| R3-202405 | (TP for [NR_SON_MDT] BL CR for TS 38.413)Addition of RACH OPTIMIZATION | ZTE |
| R3-202406 | (TP for [NR_SON_MDT] BL CR for TS 38.423)Addition of RACH OPTIMIZATION | ZTE |
| R3-202407 | (TP for [NR_SON_MDT] BL CR for TS 38.463)Addition of RACH OPTIMIZATION | ZTE |
| R3-202408 | (TP for [NR_SON_MDT] BL CR for TS 38.473)Addition of RACH OPTIMIZATION | ZTE |
| R3-202469 | CB: # 1008_Email_SON-MDT_MDT | Nokia - Moderator |
| R3-202638 | CB: # 1008_Email_SON-MDT_MDT | Nokia - Moderator |
| R3-202748 | (TP for MDT BL CR for 38.473) Correction for Cell Traffic Trace message and MDT configuration | Samsung R&D Institute UK |
| R3-202785 | (TP for MDT BL CR for TS 38.413): Clean up FFSes in MDT BLCR | Huawei,CMCC |
| R3-202790 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE |
| R3-202791 | (TP for [NR_SON_MDT] BL CR for TS 38.463): Addition of MDT | ZTE |
| R3-202826 | (TP for MDT BL CR for TS 38.423) Remaining issues in MDT | Qualcomm Incorporated |
| R3-202868 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | ZTE |
| 10.3.2 | MDT for Inactive UEs | |
| R3-202261 | Logged MDT availability indicator signal over Xn | Ericsson |
| R3-202470 | CB: # 1009_Email_SON-MDT_MDT_Inactive | Ericsson - Moderator |
| R3-202639 | CB: # 1009_Email_SON-MDT_MDT_Inactive | Ericsson - Moderator |
| 10.3.3 | MDT for MR-DC | |
| R3-202262 | User consent propagation updates for stage 2 MDT | Ericsson |
| R3-202409 | Left issue for EN-DC MDT | ZTE |
| R3-202471 | CB: # 1010_Email_SON-MDT_MDT_MRDC | ZTE - Moderator |
| R3-202640 | CB: # 1010_Email_SON-MDT_MDT_MRDC | ZTE - Moderator |
| R3-202830 | User consent propagation updates for stage 2 MDT | Ericsson |
| R3-202870 | User consent propagation updates for stage 2 MDT | Ericsson |
| 10.3.5 | Specification of Layer 2 Measurements | |
| R3-202256 | Measurement Configuration updates on NGAP TP | Ericsson |
| R3-202257 | Measurement Configuration updates on Xn TP | Ericsson |
| R3-202260 | Averaging interval Discussion | Ericsson |
| R3-202410 | L2 measurement | ZTE |
| 13.1 | General | |
| R3-201529 | BL CR to 38.423: Support for IAB | Samsung |
| R3-201530 | BL CR to 38.463: Support for IAB | Huawei |
| R3-201531 | BL CR to 38.425: Support for IAB | Samsung |
| R3-201532 | BL CR to 36.413: Support for IAB | Huawei |
| R3-201533 | draftCR TS 38.300 Mapping of Uplink Traffic to Backhaul RLC Channels | Ericsson |
| R3-201534 | BL CR to 38.413: Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-201559 | Support for IAB | Nokia, Nokia Shanghai Bell |
| R3-201596 | BL CR to 36.423: Support for IAB | Samsung |
| R3-201597 | BL CR to 38.401 Support for IAB | Huawei |
| R3-201598 | BL CR to 38.470: Support for IAB | Ericsson |
| R3-201621 | BL CR to 38.473: Support for IAB | Ericsson |
| R3-201777 | IAB workplan update | Qualcomm Incorporated (Rapporteur) |
| R3-201778 | Notation of IAB terminology | Qualcomm Incorporated (Rapporteur) |
| R3-202472 | CB: # 0_Email_IAB_BLs | Qualcomm - Moderator |
| R3-202647 | BL CR to 38.425: Support for IAB | Samsung |
| R3-202724 | CB: # 0_Email_IAB_BLs | Qualcomm - Moderator |
| R3-202757 | (TP for NR-IAB BL CR for TS 38.470): Correction | Ericsson |
| R3-202758 | (TP for NR-IAB BL CR for TS 38.300): Correction | Ericsson |
| R3-202895 | BL CR to 36.423: Support for IAB | Samsung |
| R3-202896 | BL CR to 38.401 Support for IAB | Huawei |
| R3-202897 | BL CR to 38.470: Support for IAB | Ericsson |
| R3-202898 | BL CR to 38.473: Support for IAB | Ericsson |
| R3-202929 | draftCR TS 38.300 Mapping of Uplink Traffic to Backhaul RLC Channels | Ericsson |
| 13.2.1.1 | IAB Node Integration | |
| R3-201779 | (TP for NR_IAB BL CR TS 38.401) Remaining issues on topology discovery for IAB | Qualcomm Incorporated |
| R3-202060 | (TP for NR-IAB BL CR for 38.401) Stage 2 clean-up for IAB integration procedure | Samsung |
| R3-202061 | (TP for NR-IAB BL CR for 38.401) Discussions on topology discovery | Samsung |
| R3-202062 | BL CR to 36.420: Support for IAB | Samsung |
| R3-202081 | (TP for NR_IAB BL CR for TS 38.401): Remaining issue of the IAB topology discovery | Huawei |
| R3-202082 | Draft LS to RAN2 on the IAB topology discovery | Huawei |
| R3-202246 | (TP for NR-IAB BL CR for TS 38.473) IAB-node BAP Address reporting in F1 Setup | Google Inc. |
| R3-202306 | (TP for NR-IAB BL CR for TS 38.401): Cleanups | Ericsson |
| R3-202307 | (TP for NR-IAB BL CR for TS 38.473): IAB Topology Discovery | Ericsson |
| R3-202430 | (TP for NR-IAB BL CR for TS 38.401) Misc corrections for TS38.401 | Nokia, Nokia Shanghai Bell |
| R3-202442 | Discussion on F1 removal and BAP entity release | CATT |
| R3-202473 | CB: # 1_Email_IAB_TopolDisc | Ericsson - Moderator |
| R3-202474 | CB: # 2_Email_IAB_st2_cleanups | Samsung - Moderator |
| R3-202475 | CB: # 3_Email_IAB_X2_st2 | Samsung - Moderator |
| R3-202476 | CB: # 4_Email_IAB_BAPrelease | CATT - Moderator |
| R3-202642 | (TP for NR-IAB BL CR for 38.401) Stage 2 clean-up for IAB integration procedure | Samsung |
| R3-202643 | BL CR to 36.420: Support for IAB | Samsung |
| R3-202648 | (TP for NR_IAB BL CR for TS 38.473): F1AP Cleanups | Huawei |
| R3-202664 | (TP for NR-IAB BL CR for 38.401) Stage 2 clean-up for IAB integration procedure | Samsung |
| R3-202759 | (TP for NR-IAB BL CR for TS 38.473): IAB Topology Discovery | Ericsson |
| R3-202836 | (TP for NR-IAB BL CR for 38.401) Stage 2 clean-up for IAB integration procedure | Samsung |
| 13.2.1.2 | Adaptation, QoS, Bearer Setup | |
| R3-201781 | (TP to NR_IAB BL CR 38473) IAB bearer-mapping configuration | Qualcomm Incorporated |
| R3-202017 | (TP for NR_IAB BL CR for TS 38.473): Left configuration issues for donor-DU F1 setup | ZTE, Sanechips |
| R3-202018 | (TP for NR_IAB BL CR for TS 38.473): Routing Selection Configuration at donor DU | ZTE, Sanechips |
| R3-202019 | (TP for NR_IAB BL CR for TS 38.473): Bearer Mapping Configuration | ZTE, Sanechips |
| R3-202020 | Discussion on topology discovery | ZTE, Sanechips |
| R3-202022 | Remaining issues on bearer mapping and routing configuration | ZTE, Sanechips |
| R3-202063 | (TP for NR-IAB BL CR for 38.473) Mapping configuration for intra-donor and intermediate IAB node | Samsung |
| R3-202064 | (TP for NR-IAB BL CR for 38.473) Remaining issues except bearer mapping configuration | Samsung |
| R3-202083 | (TP for NR_IAB BL CR for TS38.473): BAP configuration for IAB donor DU | Huawei |
| R3-202084 | (TP for NR_IAB BL CR for TS38.473): BH mapping configuration for intermediate IAB nodes | Huawei |
| R3-202085 | (TP for NR_IAB BL CR for TS38.473): BH mapping configuration for control PDU | Huawei |
| R3-202086 | (TP for NR-IAB BL CR for TS 38.473): Remaining issues for BH RLC channel management | Huawei |
| R3-202308 | (TP for NR-IAB BL CR for TS 38.473): Backhaul RLC Channel Mapping Configuration for IAB-nodes | Ericsson |
| R3-202309 | (TP for NR-IAB BL CR for TS 38.473): Cleanups | Ericsson |
| R3-202431 | (TP for NR-IAB BL CR for TS 38.473) Configure Donor-DU BAP Address in the Donor-DU | Nokia, Nokia Shanghai Bell |
| R3-202432 | (TP for NR-IAB BL CR for TS 38.473) BH RLC channel mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell |
| R3-202477 | CB: # 5_Email_IAB_BAPconfig_of_donor_DU | Nokia - Moderator |
| R3-202478 | CB: # 6_Email_IAB_bearer_mapping | Nokia - Moderator |
| R3-202479 | CB: # 7_Email_IAB_F1AP_cleanups | Huawei - Moderator |
| R3-202682 | CB: # 7_Email_IAB_F1AP_cleanups | Huawei - Moderator |
| R3-202747 | (TP for NR-IAB BL CR for TS 38.473) Configure Donor-DU BAP Address in the Donor-DU | Nokia, Nokia Shanghai Bell |
| R3-202788 | (TP for NR-IAB BL CR for TS 38.473) BH RLC channel mapping configuration in Donor-DU and intermediate IAB nodes | Nokia, Nokia Shanghai Bell |
| 13.2.1.3 | IP Address Management | |
| R3-201780 | DL mapping at IAB-donor-DU | Qualcomm Incorporated |
| R3-202025 | (TP for NR_IAB BL CR for TS 38.473): IP address allocation | ZTE, Sanechips |
| R3-202027 | Discussion on the left issues for IP address allocation | ZTE, Sanechips |
| R3-202065 | (TP for NR-IAB BL CR for 38.473) Remaining issues on IP address management | Samsung |
| R3-202066 | (TP for NR-IAB BL CR for 38.401) Remaining issues on IP address management | Samsung |
| R3-202067 | [Draft] LS on RRC signalling design impact of IAB | Samsung |
| R3-202087 | (TP for NR-IAB BL CR for TS 38.473) :IP address management for IAB node | Huawei |
| R3-202310 | (TP for NR-IAB BL CR for TS 38.473): IP Address Allocation for IAB-nodes | Ericsson |
| R3-202311 | [Draft] LS on RRC Message Design for IAB IP Address Allocation | Ericsson |
| R3-202433 | Discussion on remaining issues for IP address management | Nokia, Nokia Shanghai Bell |
| R3-202460 | Response to R3-202065 | Nokia, Nokia Shanghai Bell |
| R3-202480 | CB: # 8_Email_IAB_IPaddr_mgmt | Ericsson - Moderator |
| R3-202719 | (TP for NR-IAB BL CR for TS 38.401): IAB IP Address allocation | Ericsson |
| R3-202720 | (TP for NR-IAB BL CR for TS 38.473): IP Address Allocation for IAB-nodes | Ericsson |
| R3-202721 | [Draft] LS on RRC Message Design for IAB IP Address Allocation | Ericsson |
| R3-202842 | (TP for NR-IAB BL CR for TS 38.401): IAB IP Address allocation | Ericsson |
| R3-202843 | (TP for NR-IAB BL CR for TS 38.473): IP Address Allocation for IAB-nodes | Ericsson |
| R3-202844 | [Draft] LS on RRC Message Design for IAB IP Address Allocation | Ericsson |
| R3-202857 | (TP for NR-IAB BL CR for TS 38.473): IP Address Allocation for IAB-nodes | Ericsson |
| R3-202858 | RRC Message Design for IAB IP Address Allocation | Ericsson |
| R3-202926 | RRC Message Design for IAB IP Address Allocation | Ericsson |
| 13.2.1.4 | IAB-Specific Physical Layer Parameter Handling in F1AP | |
| R3-202030 | (TP for NR_IAB BL CR for TS 38.473): PHY Layer parameters configuration | ZTE, Sanechips |
| R3-202088 | (TP for NR-IAB BL CR for TS 38.473) : Cell-specific signals/channels configuration of child IAB-DU | Huawei |
| R3-202481 | CB: # 9_Email_IAB_PHY_param | ZTE - Moderator |
| R3-202750 | (TP for NR_IAB BL CR for TS 38.473): PHY Layer parameters configuration | ZTE, Sanechips |
| R3-202850 | (TP for NR_IAB BL CR for TS 38.473): PHY Layer parameters configuration | ZTE, Sanechips |
| R3-202852 | LS on cell-specific signals/channel configurations | ZTE |
| R3-202859 | LS on cell-specific signals/channel configurations | ZTE |
| 13.2.1.5 | Others | |
| R3-201696 | Considerations on BAP entity release | KDDI Corporation |
| 13.2.4 | DC Operation with IAB | |
| R3-201782 | IAB - Establishment of F1-C over LTE | Qualcomm Incorporated |
| R3-202032 | (TP for NR_IAB BL CR for TS 36.423): Support of F1-C signalling over LTE leg | ZTE, Sanechips |
| R3-202068 | (TP for NR-IAB BL CR for 36.423) Further discussion on F1AP over X2 | Samsung |
| R3-202090 | Remaining issues for F1AP over LTE | Huawei |
| R3-202434 | (TP for NR-IAB BL CR for TS 36.423) Fix the remaining issues for F1-C Traffic transfer over X2 interface | Nokia, Nokia Shanghai Bell |
| R3-202482 | CB: # 10_Email_IAB_DC_operation | Nokia - Moderator |
| R3-202789 | (TP for NR-IAB BL CR for TS 36.423) TP to clarify the F1-C traffic over LTE leg | Nokia, Nokia Shanghai Bell |
| 13.2.5 | Others | |
| R3-202089 | (TP for NR-IAB BL CR for TS 38.401): Miscellaneous change for stage 2 cleanup | Huawei |
| 13.3.2 | IAB Node Migration | |
| R3-202483 | CB: # 11_Email_IAB_node_migration | ZTE - Moderator |
| 13.3.2.1 | Functions and Criteria | |
| R3-202091 | (TP for NR-IAB BL CR for TS 38.463): IP address update when IAB topology change | Huawei |
| R3-202092 | (TP for NR-IAB BL CR for TS 38.473):IP address update when IAB topology change | Huawei |
| 13.3.2.2 | Under the Same Donor | |
| R3-202034 | (TP for NR_IAB BL CR for TS 38.401): Intra IAB donor-CU Topology Adaptation Procedure | ZTE,Sanechips |
| R3-202059 | Discussion on left issues on intra-CU migration | ZTE, Sanechips |
| R3-202751 | (TP for NR_IAB BL CR for TS 38.401): Intra IAB donor-CU Topology Adaptation Procedure | ZTE,Sanechips |
| R3-202752 | (Draft) LS on UL F1-C traffic mapping for intra-CU migration scenario | ZTE |
| R3-202851 | LS on UL F1-C traffic mapping for intra-CU migration scenario | ZTE |
| 13.3.3 | Others | |
| R3-202093 | (TP for NR-IAB BL CR for TS 38.401) : IAB-node migration in EN-DC | Huawei |
| R3-202841 | (TP for NR-IAB BL CR for TS 38.401) : IAB-node migration in EN-DC | Huawei |
| R3-202860 | (TP for NR-IAB BL CR for TS 38.401) : IAB-node migration in EN-DC | Huawei |
| 14.1 | General | |
| R3-201535 | Introduction of NBIOT dedicated CP functions when connected to 5GC | Nokia, Nokia Shanghai Bell |
| R3-201536 | Introduction of Suspend-Resume for 5GC | Nokia, Nokia Shanghai Bell |
| R3-201537 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson, Huawei, Qualcomm Incorporated |
| R3-201538 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-201539 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated |
| R3-201540 | Introduction of CP UP NB-IoT Others | Huawei |
| R3-201541 | Common CP/UP aspects of CIoT UEs when connected to 5GC | Ericsson, ZTE |
| R3-201542 | Introduction of NB-IoT related NG-AP procedures | Huawei |
| R3-201543 | Introduction of CP UP NB-IoT Others | Huawei |
| R3-201550 | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | LG Electronics |
| R3-201551 | CR for 36.423 on NB-IoT PRACH configuration exchange over X2AP | ZTE, Ericsson, Huawei |
| R3-201560 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-201561 | Support of RLF in NB-IoT | Huawei, ZTE, CMCC, Ericsson |
| R3-201582 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson |
| R3-201583 | Introduction of eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG |
| R3-201620 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-202484 | CB: # NBIOT-MTC1_Email_MTC_NB-IoT_BLs | Ericsson - Moderator |
| R3-202573 | [TP to BL CR#0188 "Introduction of Suspend Resume" for TS 38.413] Correction of coverage enhancement in suspend resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-202878 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson, Huawei, Qualcomm Incorporated |
| R3-202879 | Common CP/UP aspects of CIoT UEs when connected to 5GC | Ericsson, ZTE |
| R3-202880 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-202881 | Introduction of Suspend-Resume | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-202882 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated |
| R3-202883 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson |
| R3-202884 | Introduction of eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG |
| R3-202885 | Introduction of NB-IoT related NG-AP procedures | Huawei |
| R3-202886 | Introduction of CP UP NB-IoT Others | Huawei |
| 14.2 | Support for Mobile-Terminated Early Data Transmission | |
| R3-201759 | (TP for BL CRxx for 36.413 on MT EDT) Correction of MT EDT | Nokia, Nokia Shanghai Bell |
| R3-201799 | (TP to BL CR#1682 / 36.413 on MT-EDT) MT-EDT final aspects | Qualcomm Incorporated |
| R3-202485 | CB: # NBIOT-MTC2_Email_MT_EDT | Qualcomm - Moderator |
| 14.3.2.1 | UE Identifier for CP and UP | |
| R3-201683 | (TP to BL CR#0182 “Introduction of Suspend-Resume” for TS 38.423) UE identifier for UP CIoT 5GS Optimisation | Huawei |
| R3-201722 | (TP to BL CR#0120 Introduction of NB-IoT Paging and eDRX aspects for TS38.413): Removal of NB-IoT UE Identity Index IE | ZTE, Huawei, Ericsson |
| R3-201773 | (TP for BL CR 38.423 on Suspend Resume) Correction of Xn Suspend Resume with IRNTI | Nokia, Nokia Shanghai Bell |
| R3-201802 | (TP to BL CR#0156 / 38.413 on NB-IOT NGAP procedures) FFS Removal on 5G-S-TMSI | Qualcomm Incorporated |
| R3-202281 | TP to BL CR#0182 “Introduction of Suspend-Resume” for TS 38.423: UE identifier for UP CIoT 5GS Optimisation | LG Electronics |
| R3-202486 | CB: # NBIOT-MTC3_Email_UEidentifier_CPUP | Huawei - Moderator |
| 14.3.2.2 | eMTC RRC_INACTIVE Support | |
| R3-201684 | (TP to BL CR#0172 “Introduction of eMTC connected to 5GC” for TS38.413) Paging aspects for RRC_INACTIVE state | Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-201685 | Introduction of eMTC connected to 5GC | Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-202487 | CB: # NBIOT-MTC4_Email_MTC_Inactive | Huawei - Moderator |
| 14.3.2.3 | Support for Coverage Enhancement | |
| R3-201686 | (TP to BL CR#0153 “Common CP/UP aspects of CIoT UEs when connected to 5GC” for TS38.413) Support of Coverage Enhancement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-202488 | CB: # NBIOT-MTC5_Email_Coverage_Enhancement | Huawei - Moderator |
| R3-202597 | (TP to BL CR#0153 “Common CP/UP aspects of CIoT UEs when connected to 5GC” for TS38.413) Support of Coverage Enhancement | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| 14.3.2.4 | Update of Connection Establishment Indication | |
| R3-201774 | (TP for BL CR173 for 38.413 on CP CIoT common NBIOT/MTC) Correction of Connection Establishment Indication | Nokia, Nokia Shanghai Bell |
| R3-202189 | Removal of Connection Establishment Indication | Ericsson |
| R3-202489 | CB: # NBIOT-MTC6_Email_Connection_Establishment_Indication | Nokia - Moderator |
| R3-202565 | (TP for BL CR173 for 38.413 on CP CIoT common NBIOT/MTC) Correction of Connection Establishment Indication | Nokia, Nokia Shanghai Bell |
| 14.3.2.5 | Immediate Transition to Suspension | |
| R3-201723 | (TP to BL CR #0188 Introduction of Suspend-Resume for 5GC (UP common part) for TS38.413): Delete the UE CONTEXT SUSPEND FAILURE procedure | ZTE |
| R3-201800 | (TP to BL CR#0188 / 38.413 on Suspend-Resume) Introduction of immediate transition to suspension | Qualcomm Incorporated |
| R3-202187 | Discussion on immediate release with AS-RAI for MO-EDT in 5GC | Ericsson |
| R3-202279 | Discussion on support of early data transmission in 5GS | LG Electronics |
| R3-202280 | TP to BL CR#0188 “Introduction of Suspend-Resume for 5GC (UP common part)” for TS 38.413: Support of MO-EDT for UP CIoT 5GS optimization | LG Electronics |
| R3-202490 | CB: # NBIOT-MTC7_Email_Immediate_Transitionto_Suspension | LG - Moderator |
| R3-202656 | (TP to BL CR#0188 / 38.413 on Suspend-Resume) Introduction of immediate transition to suspension | Qualcomm Incorporated |
| 14.3.2.6 | Pending Data and UE Differentiation | |
| R3-202188 | Introduction of Pending data indication and UE subscription-based differentiation to support CIoT connected to 5GC | Ericsson |
| R3-202491 | CB: # NBIOT-MTC8_Email_Pendingdata_UEdiffer | Ericsson - Moderator |
| R3-202581 | Introduction of Pending data indication and UE subscription-based differentiation to support CIoT connected to 5GC | Ericsson |
| 14.3.2.7 | D-PUR | |
| R3-201724 | (TP to BL CR#0144 Introduction of CP UP NB-IoT Others) Support Core Network awareness of D-PUR configuration | ZTE |
| R3-201725 | CR36.413 for support of MME awareness of D-PUR configuration | ZTE |
| R3-202492 | CB: # NBIOT-MTC9_Email_D-PUR | ZTE - Moderator |
| 14.3.2.8 | UE Specific DRX | |
| R3-201687 | (TP to BL CR#0120 " Introduction of NB-IoT Paging and eDRX aspects " for TS38.413) NB-IoT UE specific DRX | Huawei, Vodafone |
| R3-201688 | Introduction of NB-IoT UE specific DRX in EPS | Huawei, Vodafone |
| R3-201689 | [DRAFT] Reply LS on Rel-16 NB-IoT enhancements | Huawei |
| R3-201726 | (TP to BL CR#0120 Introduction of NB-IoT Paging and eDRX aspects for TS38.413) Support NB-IoT UE Specific DRX | ZTE |
| R3-201727 | CR 36.413 for Support NB-IoT UE Specific DRX | ZTE |
| R3-201728 | [Draft] Reply LS on Rel-16 NB-IoT enhancements | ZTE |
| R3-202493 | CB: # NBIOT-MTC10_Email_UE_Specific_DRX | ZTE - Moderator |
| R3-202618 | CR 36.413 for Support NB-IoT UE Specific DRX | ZTE |
| R3-202619 | (TP to BL CR#0120 " Introduction of NB-IoT Paging and eDRX aspects " for TS38.413) NB-IoT UE specific DRX | Huawei, Vodafone |
| 14.3.2.9 | Others | |
| R3-201716 | (TP to BL CR#0157 “Introduction of CP UP NB-IoT Others” for TS 38.413) Overload Action | Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-201747 | (TP to BL CR#0156 “Introduction of NB-IoT related NG-AP procedures” for TS 38.413) 5G-S-TMSI in Error Indication | Huawei |
| R3-201801 | (TP to BL CR#0156 / 38.413 on NB-IOT NGAP procedures) Alignment of NB-IOT RAT information towards AMF | Qualcomm Incorporated |
| R3-202494 | CB: # NBIOT-MTC11_Email_others | Qualcomm - Moderator |
| 14.5.1 | Group WUS | |
| R3-201676 | Consideration on UE group wake up signal (WUS) | Huawei, Vodafone |
| R3-201677 | Support of WUS Group | Huawei, Vodafone |
| R3-201678 | [Draft]Reply LS on assistance indication for WUS | Huawei |
| R3-202190 | Introduction of WUS grouping | Ericsson, ZTE |
| R3-202191 | Introduction of WUS grouping | Ericsson, ZTE |
| R3-202495 | CB: # NBIOT-MTC12_Email_Group_WUS | Ericsson - Moderator |
| R3-202580 | Support of WUS Group | Huawei, Vodafone |
| 15.1 | General | |
| R3-201544 | Baseline CR for introducing Rel-16 LTE further mobility enhancement | Intel Corporation |
| R3-201545 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-201554 | TS38.470 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-201565 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom |
| R3-201571 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | CATT, Nokia, Nokia Shanghai Bell |
| R3-201572 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, Nokia, Nokia Shanghai Bell |
| R3-201584 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-201585 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-201586 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-201587 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation, CATT, ZTE, Huawei |
| R3-201588 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-201589 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, CATT |
| R3-201653 | (TP for NR_Mob_enh BL CR for TS 38.423): Clean-up of the BL CR | Nokia, Nokia Shanghai Bell |
| R3-202496 | CB: # 12_Email_MobEnh_BLs_cleanups | Huawei - Moderator |
| R3-202574 | TS38.470 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-202575 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom |
| R3-202675 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | CATT, Nokia, Nokia Shanghai Bell |
| R3-202676 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, Nokia, Nokia Shanghai Bell |
| R3-202713 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-202714 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation |
| R3-202734 | (TP for NR_Mob_enh BL CR for TS 38.423): Clean-up of the BL CR | Nokia, Nokia Shanghai Bell |
| R3-202796 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, CATT |
| R3-202887 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation |
| R3-202888 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-202907 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom |
| R3-202908 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation, CATT, ZTE, Huawei |
| R3-202909 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-202910 | Baseline CR for introducing Rel-16 NR mobility enhancement | Ericsson, CATT |
| R3-202930 | Baseline CR for introducing Rel-16 NR mobility enhancement | CATT, Nokia, Nokia Shanghai Bell |
| R3-202931 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | CATT, Nokia, Nokia Shanghai Bell |
| 15.2.1 | Common | |
| R3-201637 | TP for E-UTRA_Mob_enh BL CR for TS 36.423 Correction of Mis-usage of SN Status Transfer Message | ZTE |
| R3-201638 | TP for NR_Mob_enh BL CR for TS 38.423 Correction of Mis-usage of SN Status Transfer Message | ZTE |
| R3-201731 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Resolving FFS Issues with DAPS Response Information | ZTE |
| R3-201732 | (TP for NR_Mob_enh BL CR for TS 38.423) Resolving FFS Issues with DAPS Response Information | ZTE |
| R3-201873 | (TP for NR_Mob_enh BL CR for TS 38.413): Left issues for DAPS handover | Huawei |
| R3-201874 | (TP for LTE_feMob-Core BL CR for TS 36.413): Left issues for DAPS handover | Huawei |
| R3-201875 | Left issues for DAPS handover | Huawei |
| R3-201940 | Remaining Issues for DAPS HO | CATT |
| R3-201941 | (TP for [LTE_feMob] BL CR for TS 36413)Remaining Issues for DAPS HO | CATT |
| R3-201942 | (TP for [NR_Mob_enh] BL CR for TS 38413)Remaining Issues for DAPS HO | CATT |
| R3-201943 | (TP for [LTE_feMob] BL CR for TS 36423)Remaining Issues for DAPS HO | CATT |
| R3-201944 | (TP for [NR_Mob_enh] BL CR for TS 38423)Remaining Issues for DAPS HO | CATT |
| R3-201945 | CR to TS 38.463 for Remaining Issues for DAPS HO | CATT |
| R3-202007 | Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202008 | (TP for LTE_feMob BL CR for TS 36.300) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202009 | (TP for LTE_feMob BL CR for TS 36.423) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202010 | (TP for NR_Mob_enh BL CR for TS 38.300) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202011 | (TP for NR_Mob_enh BL CR for TS 38.423) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202181 | (TP for LTE_Mob_enh BL CR for TS 36.423) Introduce fallback information per E-RAB for LTE | China Telecommunication |
| R3-202182 | (TP for NR_Mob_enh BL CR for TS 38.423) Discussion on DAPS indicator and introduce fallback information per DRB for NR | China Telecommunication |
| R3-202252 | (TP for NR_Mob_enh BL CR for TS 38.423): Consideration on the fallback indication | Nokia, Nokia Shanghai Bell |
| R3-202253 | (TP for LTE_feMob BL CR for TS 36.423): Consideration on the fallback indication | Nokia, Nokia Shanghai Bell |
| R3-202288 | DAPS HO handling during preparation | Intel Corporation |
| R3-202289 | (TP for LTE_feMob-Core BL CR for TS 36.423): DAPS HO handling during preparation | Intel Corporation |
| R3-202290 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): DAPS HO handling during preparation | Intel Corporation |
| R3-202291 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): DAPS HO handling during preparation | Intel Corporation |
| R3-202292 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): DAPS HO handling during preparation | Intel Corporation |
| R3-202361 | (TP for LTE_feMob BL CR for TS 36.413): Support of S1 and NG DAPS HO | Ericsson |
| R3-202362 | (TP for NR Mob BL CR for TS 38.413): Support of NG DAPS HO | Ericsson |
| R3-202363 | (TP for NR Mob BL CR for TS 38.423): DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-202364 | (TP for LTE_feMob BL CR for TS 36.423): DAPS HO - per-DRB Handover Preparation | Ericsson |
| R3-202365 | (TP for NR Mob BL CR for TS 38.300): DAPS HO - PDCP SN continuity for RLC-UM | Ericsson |
| R3-202366 | (TP for LTE_feMob BL CR for TS 36.300): DAPS HO - PDCP SN continuity for RLC-UM | Ericsson |
| R3-202424 | (TP for NR_Mob_enh BL CR for TS 38.423): Left issues for DAPS handover | Huawei |
| R3-202425 | (TP for LTE_feMob-Core BL CR for TS 36.423): Left issues for DAPS handover | Huawei |
| R3-202427 | Consideration on FFSs for DAPS handover | LG Electronics |
| R3-202452 | CR for introducing Rel-16 NR mobility enhancement | CATT, CMCC |
| R3-202497 | CB: # 13_Email_MobEnh_DAPS_X2XnE1 | Intel - Moderator |
| R3-202498 | CB: # 14_Email_MobEnh_Common_PDCP_SN_Continuity_RLC-UM | Ericsson - Moderator |
| R3-202660 | (TP for [NR_Mob_enh] BL CR for TS 38413)Remaining Issues for DAPS HO | CATT |
| R3-202661 | (TP for LTE_feMob BL CR for TS 36.413): Support of S1 and NG DAPS HO | Ericsson |
| R3-202678 | (TP for LTE_feMob BL CR for TS 36.300) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202679 | (TP for NR_Mob_enh BL CR for TS 38.300) Clarification of supporting PDCP SN continuity for RLC-UM bearer in DAPS HO | Samsung |
| R3-202715 | (TP for LTE_feMob-Core BL CR for TS 36.423): DAPS HO handling during preparation | Intel Corporation |
| R3-202716 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): DAPS HO handling during preparation | Intel Corporation |
| 15.2.3 | NR | |
| R3-201795 | (TP for NR_Mob_enh BL CR for TS 38.423) Remaining issues in DAPS handover over Xn | Qualcomm Incorporated |
| R3-201796 | (TP for NR_Mob_enh BL CR for TS 38.413) Handover Success procedure for NGAP based DAPS handover | Qualcomm Incorporated |
| R3-201797 | Remaining issues for DAPS handover over NG | Qualcomm Incorporated |
| R3-202499 | CB: # 16_Email_MobEnh_DAPS_S1NG | CATT - Moderator |
| R3-202709 | LS on S1/NG DAPS handover | CATT |
| R3-202835 | LS on S1/NG DAPS handover | CATT |
| R3-202845 | LS on S1/NG DAPS handover | CATT |
| R3-202932 | LS on S1/NG DAPS handover | CATT |
| 15.3.1 | Common | |
| R3-201660 | Continuation of the work on CHO for NG- and S1-based handover (incl. TPs for NGAP and S1AP BL CRs) | Nokia, Nokia Shanghai Bell |
| 15.3.1.1 | Conditional PSCell Change | |
| R3-201656 | Avoiding simultaneous CHO and CPC | Nokia, Nokia Shanghai Bell |
| R3-201657 | (TP for NR_Mob_enh BL CR for TS 38.423): A solution to enable the MN to block CPC usage | Nokia, Nokia Shanghai Bell |
| R3-201658 | (TP for LTE_feMob BL CR for TS 36.423): A solution to enable the MN to block CPC usage | Nokia, Nokia Shanghai Bell |
| R3-201659 | Response LS on avoiding simultaneous CHO and CPC | Nokia, Nokia Shanghai Bell |
| R3-201798 | Avoiding simultaneous CHO and CPC | Qualcomm Incorporated |
| R3-201876 | (TP for NR_Mob_enh BL CR for TS 38.423): Avoidance of simultaneous CHO and CPC configuration | Huawei |
| R3-201877 | (TP for LTE_feMob BL CR for TS 36.423): Avoidance of simultaneous CHO and CPC configuration | Huawei |
| R3-201878 | (TP for NR_Mob_enh BL CR for TS 37.340): Avoidance of simultaneous CHO and CPC configuration | Huawei |
| R3-201879 | (TP for NR_Mob_enh BL CR for TS 38.401): RRCReconfigurationComplete Transfer in Conditional Pscell Change | Huawei |
| R3-201890 | (TP for NR_Mob_enh BL CR for TS 37.340) Further Discussion of Parallel CHO and CPC Simultaneous Operation | ZTE, China Telecom, China Unicom |
| R3-201891 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Introduction of Maximum Number of Candidate PScells Allowed by MN | ZTE, China Telecom, China Unicom |
| R3-201892 | (TP for NR_Mob_enh BL CR for TS 38.423) Introduction of Maximum Number of Candidate PScells Allowed by MN | ZTE, China Telecom, China Unicom |
| R3-201946 | Issue of Avoiding Simultaneous CHO and CPC | CATT |
| R3-201947 | (TP for [LTE_feMob] BL CR for TS 36423)Issue of Avoiding Simultaneous CHO and CPC | CATT |
| R3-201948 | (TP for [NR_Mob_enh] BL CR for TS 38423)Issue of Avoiding Simultaneous CHO and CPC | CATT |
| R3-202076 | Supporting Conditional PSCell Change using MCG SRB | Samsung |
| R3-202077 | (TP for NR_Mob_enh BL CR for TS 38.401) Supporting Conditional PSCell Change using MCG SRB | Samsung |
| R3-202078 | (TP for LTE_feMob BL CR for TS 36.423) Supporting Conditional PSCell Change using MCG SRB | Samsung |
| R3-202079 | (TP for NR_Mob_enh BL CR for TS 38.423) Supporting Conditional PSCell Change using MCG SRB | Samsung |
| R3-202243 | Discussion on avoiding simultaneous CHO and CPC configuration | Google Inc. |
| R3-202244 | (TP for LTE_feMob BL CR for TS 36.423) RRC Reconfiguration Complete for CPC | Google Inc. |
| R3-202245 | (TP for NR_Mob_enh BL CR for TS 38.423) RRC Reconfiguration Complete for CPC | Google Inc. |
| R3-202293 | Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| R3-202294 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| R3-202295 | (TP for LTE_feMob-Core BL CR for TS 36.423): Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| R3-202296 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| R3-202500 | CB: # 17_Email_MobEnh_CHO_CondPSCell_General | Intel - Moderator |
| R3-202501 | CB: # 18_Email_MobEnh_Avoid_CHO_and_CondPSCellChg | Nokia - Moderator |
| R3-202717 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| R3-202762 | (TP for NR_Mob_enh BL CR for TS 37.340) Further Discussion of Parallel CHO and CPC Simultaneous Operation | ZTE, China Telecom, China Unicom |
| R3-202855 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| R3-202871 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Correction and Resolving FFS on inter-gNB-DU conditional mobility scenarios | Intel Corporation |
| 15.3.1.2 | CHO Preparation | |
| R3-201670 | (TP for NR_Mob_enh BL CR for TS 38.401) Clarification of Multiple APID Usage in CHO and CPC | ZTE |
| R3-201671 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Further Clarification of Maximum Number of CHO Preparations | ZTE |
| R3-201672 | (TP for NR_Mob_enh BL CR for TS 38.423) Further Clarification of Maximum Number of CHO Preparations | ZTE |
| R3-202367 | (TP for NR Mob BL CR for TS 38.423) CHO in MR-DC operation | Ericsson |
| R3-202368 | (TP for NR Mob BL CR for TS 37.340) CHO in MR-DC operation | Ericsson |
| R3-202502 | CB: # 19_Email_MobEnh_CHOprep | Ericsson - Moderator |
| R3-202577 | (TP for NR_Mob_enh BL CR for TS 38.401) Clarification of Multiple APID Usage in CHO and CPC | ZTE |
| R3-202613 | (TP for E-UTRA_Mob_enh BL CR for TS 36.423) Further Clarification of Maximum Number of CHO Preparations | ZTE |
| R3-202614 | (TP for NR_Mob_enh BL CR for TS 38.423) Further Clarification of Maximum Number of CHO Preparations | ZTE |
| R3-202663 | (TP for LTE_feMob BL CR for TS 36.300) CHO in MR-DC operation | Ericsson |
| R3-202780 | (TP for NR Mob BL CR for TS 37.340) CHO in MR-DC operation | Ericsson |
| 15.3.1.3 | CHO Modification | |
| R3-201654 | (TP for NR_Mob_enh BL CR for TS 38.423): Completion of the open points related to the modification of a CHO | Nokia, Nokia Shanghai Bell |
| R3-201655 | (TP for LTE_feMob BL CR for TS 36.423): Completion of the open points related to the modification of the CHO | Nokia, Nokia Shanghai Bell |
| R3-201710 | (TP for NR_Mob_enh BL CR for TS 38.473) Introduction of New Cause Value for gNB-DU Initiated CHO Modify and Cancel | ZTE |
| R3-201714 | (TP for NR_Mob_enh BL CR for TS 38.473) Refine the Usage of UE CONTEXT MODIFICATION for Candidate Cell Modify and Cancel | ZTE |
| R3-201766 | Target initiated CHO Modification | NEC |
| R3-201794 | (TP for NR_Mob_enh BL CR for TS 38.423) Remaining issues in CHO modification | Qualcomm Incorporated |
| R3-201880 | (TP for NR_Mob_enh BL CR for TS 38.423): Target Node Initiated CHO Modification | Huawei |
| R3-201881 | (TP for LTE_feMob BL CR for TS 36.423): Target Node Initiated CHO Modification | Huawei |
| R3-202012 | Supporting the target node initiated CHO modification | Samsung |
| R3-202013 | (TP for LTE_feMob BL CR for TS 36.423) Supporting the target node initiated CHO modification | Samsung |
| R3-202014 | (TP for NR_Mob_enh BL CR for TS 38.423) Supporting the target node initiated CHO modification | Samsung |
| R3-202015 | (TP for NR_Mob_enh BL CR for TS 38.473) Supporting the target node initiated CHO modification | Samsung |
| R3-202179 | (TP for LTE_Mob_enh BL CR for TS 36.423) Target-initiated CHO Modification | China Telecommunication |
| R3-202180 | (TP for NR_Mob_enh BL CR for TS 38.423) Target-initiated CHO Modification | China Telecommunication |
| R3-202370 | CHO - Modification from target node | Ericsson |
| R3-202371 | (TP for NR Mob BL CR for TS 38.423): CHO - Modification from target node | Ericsson |
| R3-202372 | (TP for LTE_feMob BL CR for TS 36.423): CHO - Modification from target node | Ericsson |
| R3-202503 | CB: # 20_Email_MobEnh_CHOmod | Nokia - Moderator |
| R3-202578 | (TP for NR_Mob_enh BL CR for TS 38.473) Refine the Usage of UE CONTEXT MODIFICATION for Candidate Cell Modify and Cancel | ZTE |
| R3-202753 | (TP for NR_Mob_enh BL CR for TS 38.423): Completion of the open points related to the modification of a CHO | Nokia, Nokia Shanghai Bell |
| R3-202754 | (TP for LTE_feMob BL CR for TS 36.423): Completion of the open points related to the modification of the CHO | Nokia, Nokia Shanghai Bell |
| 15.3.1.5 | Overload Issues | |
| R3-202094 | Arrival probability to avoid overload due to CHO | Vodafone, Nokia, Nokia Shanghai Bell, British Telecom |
| R3-202095 | (TP for LTE_feMob BL CR for TS 36.423): Implementation of the arrival probability | Vodafone, Nokia, Nokia Shanghai Bell, British Telecom |
| R3-202096 | (TP for NR_Mob_enh BL CR for TS 38.423): Implementation of the arrival probability | Vodafone, Nokia, Nokia Shanghai Bell, British Telecom |
| R3-202504 | CB: # 21_Email_MobEnh_Overload | Vodafone - Moderator |
| R3-202671 | (TP for LTE_feMob BL CR for TS 36.423): Implementation of the arrival probability | Vodafone, Nokia, Nokia Shanghai Bell, British Telecom |
| R3-202672 | (TP for NR_Mob_enh BL CR for TS 38.423): Implementation of the arrival probability | Vodafone, Nokia, Nokia Shanghai Bell, British Telecom |
| 15.3.3 | NR | |
| R3-201715 | (TP for NR_Mob_enh BL CR for TS 38.473) Further Clean-ups for Abnormal Conditions etc | ZTE |
| R3-201717 | (TP for NR_Mob_enh BL CR for TS 38.473) Introduction of NR CGI IE into UL RRC MESSAGE TRANSFER Message | ZTE, CATT, Google |
| R3-201721 | TS38.460 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| R3-201765 | CHO in E1 interface | NEC |
| R3-201949 | Discussion on E1 impact during Conditional Handover | CATT |
| R3-201950 | CR to TS 38.463 for E1 impact during Conditional Handover | CATT |
| R3-202369 | CHO Bearer Context in CU-UP | Ericsson |
| R3-202505 | CB: # 22_Email_MobEnh_CHO_NR | ZTE - Moderator |
| R3-202579 | (TP for NR_Mob_enh BL CR for TS 38.473) Further Clean-ups for Abnormal Conditions etc | ZTE |
| R3-202692 | TS38.460 Stage2 Introduction of Mobility Enhancement Features | ZTE, China Telecom, China Unicom |
| 15.4.1 | Common | |
| R3-202416 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support over E1 | Huawei |
| 15.4.1.1 | Handover Interruption Reduction | |
| R3-202374 | Early data forwarding and CU-UP DL transmission start/stop | Ericsson |
| R3-202375 | Early data forwarding and CU-UP DL transmission start/stop | Ericsson |
| 15.4.1.2 | CHO | |
| R3-201927 | (TP for NR_Mob_enh BL CR for TS 38.423): Early Data Forwarding for CHO | Apple Inc., Intel Corporation |
| R3-201928 | (TP for LTE_feMob-Core BL CR for TS 36.423): Early Data Forwarding for CHO | Apple Inc., Intel Corporation |
| R3-201951 | Discussion on Early Data Forwarding for CHO | CATT |
| R3-202299 | Early Forwarding may need candidate cell distinction | Intel Corporation |
| R3-202300 | (TP for LTE_feMob-Core BL CR for TS 36.423): Early Forwarding may need candidate cell distinction | Intel Corporation |
| R3-202301 | (TP for NR_Mob_enh-Core BL CR for TS 38.423): Early Forwarding may need candidate cell distinction | Intel Corporation |
| R3-202302 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Early Forwarding may need candidate cell distinction | Intel Corporation |
| R3-202506 | CB: # 24_Email_MobEnh_Data_fwd_CHO | Intel - Moderator |
| R3-202718 | (TP for NR_Mob_enh-Core BL CR for TS 38.401): Early Forwarding may need candidate cell distinction | Intel Corporation |
| 15.4.3 | NR | |
| R3-202297 | Early Forwarding support for DAPS/CHO over E1 | Intel Corporation, ZTE, Google, CATT |
| R3-202298 | (TP for NR_Mob_enh-Core BL CR for TS 38.463): Early Forwarding support for DAPS/CHO over E1 | Intel Corporation, ZTE, Google, CATT |
| R3-202373 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-202377 | Optimizing multiple SN STATUS TRANSFER for disaggregated gNB | Ericsson |
| R3-202507 | CB: # 25_Email_Mob_Enh_Data_fwd_E1 | Intel - Moderator |
| 16.1 | General | |
| R3-201567 | CR to TS 38.460 on support of NPN | Huawei, China Telecom |
| R3-201568 | CR to TS 38.470 on support of NPN | Huawei, China Telecom |
| R3-201590 | Introduction of Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-201591 | BL CR NPN for 38.401 | China Telecommunication |
| R3-201592 | Introduction of Non-Public Networks | Qualcomm Incorporated |
| R3-201593 | Introduction of Non-Public Networks | Ericsson |
| R3-201594 | Introduction of Non-Public Networks for TS38.463 | ZTE |
| R3-201595 | Introduction of NPN | Huawei, China Telecom |
| R3-201775 | Information on NPN RAN2 BL CR | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-201803 | (TP for NPN BL CR#0290 for TS 38.413) Proposed rapporteur changes to the NGAP BL CR | Qualcomm Incorporated |
| R3-202174 | Updated work plan for PRN WI | China Telecommunication |
| R3-202508 | CB: # 28_Email_PRN_General_BLs_cleanups | China Telecom - Moderator |
| R3-202654 | [TP for BL CR XnAP] Corrections of BL CR along outcome of CB#28 | Ericsson |
| R3-202657 | (TP for NPN BL CR#0290 for TS 38.413) Proposed rapporteur changes to the NGAP BL CR | Qualcomm Incorporated |
| R3-202889 | Introduction of Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-202890 | Introduction of Non-Public Networks | Qualcomm Incorporated |
| R3-202891 | Introduction of Non-Public Networks | Ericsson |
| R3-202892 | Introduction of Non-Public Networks for TS38.463 | ZTE |
| R3-202893 | CR to TS 38.470 on support of NPN | Huawei, China Telecom |
| R3-202894 | Introduction of NPN | Huawei, China Telecom |
| 16.2 | Configuration Aspects | |
| R3-201763 | (TP for NPN BL CR for TS 38.413) Remaining open points on NPN | NEC |
| R3-201764 | (TP for NPN BL CR for TS 38.423) Remaining open points on NPN | NEC |
| R3-201776 | (TP for NPN BL CR 38.413) Support of CAG Configuration | Nokia, Nokia Shanghai Bell |
| R3-201804 | (TP for CR#0290 to TS38.413 Baseline CR on NPN) Resolving the FFS in configuration exchange in NGAP | Qualcomm Incorporated |
| R3-201914 | Left open issues on NG interface for NPN | ZTE Corporation |
| R3-202127 | [TP for BL CR XnAP] Alignment of NPN Broadcast Information with 38.331 v16.0.0 | Ericsson |
| R3-202335 | (TP for NPN BL CR for TS 38.413): NG Configuration aspects for NPN | Huawei |
| R3-202336 | (TP for NPN BL CR for TS 38.423): Self-configuration aspects for NPN | Huawei |
| R3-202509 | CB: # 29_Email_PRN_config | Huawei - Moderator |
| R3-202649 | (TP for NPN BL CR for TS 38.413): NG Configuration aspects for NPN | Huawei |
| R3-202650 | [TP for BL CR XnAP] Alignment of NPN Broadcast Information with 38.331 v16.0.0 | Ericsson |
| 16.3.1 | Initial UE Message | |
| R3-201805 | (TP for CR#0290 to TS38.413 Baseline CR on NPN) Resolving open issues on initial access | Qualcomm Incorporated |
| R3-201812 | (TP for NPN BL CR for 38.413) Correction of NPN Access control | Nokia, Nokia Shanghai Bell |
| R3-201813 | (TP for NPN BL CR for 38.413) Correction of NPN Access Failure | Nokia, Nokia Shanghai Bell |
| R3-202128 | [TP for BL CR NGAP] Move the NPN Access Information in INITIAL UE MESSAGE into the ULI | Ericsson |
| R3-202337 | (TP for NPN BL CR for TS 38.413): Initial UE message for NPN | Huawei |
| R3-202510 | CB: # 30_Email_PRN_initUEmessage | Ericsson - Moderator |
| R3-202615 | (TP for NPN BL CR for 38.413) Correction of NPN Access Failure | Nokia, Nokia Shanghai Bell |
| R3-202652 | [TP for BL CR NGAP] Move the NPN Access Information in INITIAL UE MESSAGE into the ULI | Ericsson |
| R3-202680 | (TP for NPN BL CR for TS 38.413): Initial UE message for NPN | Huawei |
| 16.3.2 | Mobility Restriction List | |
| R3-201814 | (TP for NPN BL CR for 38.413) Correction of MRL over NG | Nokia, Nokia Shanghai Bell |
| R3-201815 | (TP for NPN BL CR for 38.423) Correction of MRL over Xn | Nokia, Nokia Shanghai Bell |
| R3-202129 | [TP for BL CR NGAP] CN initiated update of the CAG info in the MRL | Ericsson |
| R3-202177 | (TP for TS 38.300) Clarification on Mobility Restriction List | China Telecommunication, Huawei |
| R3-202338 | (TP for NPN BL CR for TS 38.413): Mobility restriction list for NPN | Huawei |
| R3-202339 | (TP for NPN BL CR for TS 38.423): Mobility restriction list for NPN | Huawei |
| R3-202340 | Mobility restriction list for MR-DC NPN | Huawei |
| R3-202511 | CB: # 30_Email_PRN_MobRestrList | Nokia - Moderator |
| R3-202659 | (TP for TS 38.300) Clarification on Mobility Restriction List | China Telecommunication, Huawei |
| 16.4 | Mobility | |
| R3-201760 | (TP for NPN BL CR for TS 38.413) Mobility in Inactive State in NPN | NEC |
| R3-201761 | (TP for NPN BL CR for TS 38.423) Mobility in Inactive State in NPN | NEC |
| R3-201816 | (TP for NPN BL CR for 38.413) Correction of NPN Mobility over NG | Nokia, Nokia Shanghai Bell |
| R3-201817 | (TP for NPN BL CR for 38.423) Correction of NPN Mobility over Xn | Nokia, Nokia Shanghai Bell |
| R3-201921 | Mobility in inactive state | ZTE Corporation |
| R3-201922 | Consideration on selected CAG ID | ZTE Corporation |
| R3-201939 | Discussion on NPN manual network selection | CATT |
| R3-202284 | Clarification on mobility of NPN | LG Electronics |
| R3-202285 | (TP for NPN BL CR for TS 38.300): Consideration on RRC-INACTIVE in NPN | LG Electronics |
| R3-202341 | (TP for NPN BL CR for TS 38.300): Inactive mobility for NPN | Huawei |
| R3-202342 | (TP for NPN BL CR for TS 38.423): Inactive mobility for NPN | Huawei |
| R3-202343 | Mobility aspets of MR-DC NPN | Huawei |
| R3-202383 | (TP for NPN BL CR for 38.423) Access control for UE Context Retrieval in NPN | Samsung R&D Institute UK |
| R3-202512 | CB: # 31_Email_PRN_mobility_inactive | Huawei - Moderator |
| R3-202513 | CB: # 32_Email_PRN_manual_selection | LG - Moderator |
| R3-202616 | (TP for NPN BL CR for 38.423) Correction of NPN Mobility over Xn | Nokia, Nokia Shanghai Bell |
| R3-202756 | (TP for NPN BL CR for TS 38.300): Inactive mobility for NPN | Huawei |
| 16.5 | Paging | |
| R3-201818 | (TP for NPN BL CR for 38.413) Correction of NPN Paging over NG | Nokia, Nokia Shanghai Bell |
| R3-201819 | (TP for NPN BL CR for 38.423) Correction of NPN Paging over Xn | Nokia, Nokia Shanghai Bell |
| R3-202130 | Possibility to optimise CN paging for PNI-NPNs | Ericsson |
| R3-202131 | [TP for BL CR NGAP] Introduction of NG Paging Optimisation Elements for CAG-only UEs. | Ericsson |
| R3-202132 | [DRAFT] LS on CN Paging Optimisation for PNI-NPNs | Ericsson |
| R3-202178 | (TP for TS 38.413) NPN NG Paging | China Telecommunication |
| R3-202282 | Discussion on NG paging in SNPN | LG Electronics |
| R3-202283 | (TP for NPN BL CR for TS 38.413): Correction on NG paging in SNPN | LG Electronics |
| R3-202344 | (TP for NPN BL CR for TS 38.413): Paging for NPN | Huawei |
| R3-202345 | (TP for NPN BL CR for TS 38.423): Paging for NPN | Huawei |
| R3-202346 | (TP for NPN BL CR for TS 38.300): Paging for NPN | Huawei |
| R3-202514 | CB: # 33_Email_PRN_paging | Ericsson - Moderator |
| R3-202681 | (TP for NPN BL CR for TS 38.300): Paging for NPN | Huawei |
| 16.6 | F1 Aspects | |
| R3-201632 | (TP for NPN BL CR for TS 38.473): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-201633 | (TP for NPN BL CR for TS 38.470): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-201925 | Impact of NPN on F1 | ZTE Corporation |
| R3-201926 | TP for NPN support to TS38.473 | ZTE Corporation |
| R3-201938 | Discussion on F1 open issue | CATT |
| R3-202133 | Discussion on F1AP topics not covered in other AIsPlace Holder F1 Aspect | Ericsson |
| R3-202134 | [TP for BL CR F1AP] F1AP topics not covered in other Ais | Ericsson |
| R3-202173 | TP for NPN BL CR for 38.401 | China Telecommunication, Nokia, Nokia Shanghai Bell, Huawei |
| R3-202175 | (TP for TS 38.470) On F1 aspects for NPN | China Telecommunication, Nokia, Nokia Shanghai Bell |
| R3-202347 | (TP for NPN BL CR for TS 38.470): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-202348 | (TP for NPN BL CR for TS 38.473): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-202515 | CB: # 34_Email_PRN_F1 | Nokia - Moderator |
| R3-202673 | TP for NPN BL CR for 38.401 | China Telecommunication, Nokia, Nokia Shanghai Bell, Huawei |
| R3-202674 | (TP for TS 38.470) On F1 aspects for NPN | China Telecommunication, Nokia, Nokia Shanghai Bell |
| R3-202694 | (TP for NPN BL CR for TS 38.470): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-202702 | (TP for NPN BL CR for TS 38.473): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-202839 | (TP for NPN BL CR for TS 38.473): NPN for F1 | Nokia, Nokia Shanghai Bell |
| R3-202853 | TP for NPN BL CR for 38.401 | China Telecommunication, Nokia, Nokia Shanghai Bell, Huawei |
| R3-202854 | (TP for NPN BL CR for TS 38.470): Further support of NPN over F1 | Huawei, China Telecommunication |
| R3-202861 | (TP for NPN BL CR for TS 38.473): NPN for F1 | Nokia, Nokia Shanghai Bell |
| 16.7 | E1 Aspects | |
| R3-201634 | (TP for NPN BL CR for TS 38.463): NPN for E1 | Nokia, Nokia Shanghai Bell |
| R3-201635 | (TP for NPN BL CR for TS 38.460): NPN for E1 | Nokia, Nokia Shanghai Bell |
| R3-201923 | Impact of NPN on E1 | ZTE Corporation |
| R3-201924 | TP for NPN support to TS38.463 | ZTE Corporation |
| R3-202135 | Discussion on open E1AP issues for NPN | Ericsson |
| R3-202136 | [TP for BL CR E1AP] Resolving open E1AP issues for NPN | Ericsson |
| R3-202349 | (TP for NPN BL CR for TS 38.460): Further support of NPN over E1 | Huawei, China Telecommunication |
| R3-202350 | (TP for NPN BL CR for TS 38.463): Further support of NPN over E1 | Huawei, China Telecommunication |
| R3-202516 | CB: # 35_Email_PRN_E1 | Ericsson - Moderator |
| R3-202653 | [TP for BL CR E1AP] Resolving open E1AP issues for NPN | Ericsson |
| 16.8 | RAN Sharing Aspects | |
| R3-201935 | Discussion on RAN sharing for NPNs | CATT |
| R3-201936 | (TP on NPN BLCR for 38.423)Correction on RAN sharing for NPNs | CATT |
| R3-201937 | (TP on NPN BLCR for 38.473)Correction on RAN sharing for NPNs | CATT |
| R3-202137 | On the maximum number of allowed networks IDs broadcast in one physical cell | Ericsson |
| R3-202351 | (TP for NPN BL CR for TS 38.413): Support of RAN sharing with NPN: NG aspects | Huawei |
| R3-202352 | (TP for NPN BL CR for TS 38.300): Support of RAN sharing with NPN | Huawei |
| R3-202353 | (TP for NPN BL CR for TS 38.401) Support of RAN sharing with NPN: F1 aspects | Huawei |
| R3-202354 | (TP for NPN BL CR for TS 38.473): Support of RAN sharing with NPN: F1 aspects | Huawei |
| R3-202517 | CB: # 36_Email_PRN_nw_sharing | Huawei - Moderator |
| R3-202651 | (TP for NPN BL CR for TS 38.300): Support of RAN sharing with NPN | Huawei |
| 16.9 | Network Slicing Aspects | |
| R3-201636 | (TP for NPN BL CR for TS 38.473): NPN Network Slicing for F1 | Nokia, Nokia Shanghai Bell |
| R3-201762 | (TP for NPN BL CR for TS 38.473) Network Slice Support in NPN | NEC |
| R3-201820 | (TP for NPN BL CR 38.413) NPN Slicing aspects over NG | Nokia, Nokia Shanghai Bell |
| R3-202138 | [TP for BL CR 38.413] Corrections for Network Slicing for SNPNs | Ericsson |
| R3-202139 | [TP for BL CR 38.423] Corrections for Network Slicing for SNPNs | Ericsson |
| R3-202140 | [TP for BL CR 38.473] Corrections for Network Slicing for SNPNs | Ericsson |
| R3-202141 | [TP for BL CR 38.463] Corrections for Network Slicing for SNPNs | Ericsson |
| R3-202176 | On network slicing aspects | China Telecommunication |
| R3-202355 | (TP for NPN BL CR for TS 38.423): Slicing aspects for NPN | Huawei |
| R3-202356 | (TP for NPN BL CR for TS 38.463): Slicing aspects for NPN | Huawei |
| R3-202357 | (TP for NPN BL CR for TS 38.300): Slicing aspects for NPN | Huawei |
| R3-202518 | CB: # 37_Email_PRN_slicing | Nokia - Moderator |
| R3-202641 | (TP for NPN BL CR for TS 38.473): NPN Network Slicing for F1 | Nokia, Nokia Shanghai Bell, NEC |
| 17.1 | General | |
| R3-201546 | Introduction of NR_IIOT support to TS 38.415 | Nokia, Nokia Shanghai Bell |
| R3-201599 | NRIIOT Higher Layer Multi-Connectivity | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia |
| R3-201600 | Introduction of NR_IIOT support to TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei |
| R3-201601 | Introduction of NR_IIOT support to TS 38.423 | Ericsson |
| R3-201602 | Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC, Ericsson |
| R3-201603 | Introduction of NR_IIOT support to TS 38.463 | ZTE |
| R3-201604 | Introduction of NR_IIOT support to TS 38.473 | Huawei |
| R3-202142 | Correction of BL CR R3-201601 for NR_IIOT | Ericsson |
| R3-202519 | CB: # NRIIOT1_Email_NRIIOT_BLs | Nokia - Moderator |
| R3-202901 | NRIIOT Higher Layer Multi-Connectivity | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia |
| R3-202902 | Introduction of NR_IIOT support to TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei |
| R3-202903 | Introduction of NR_IIOT support to TS 38.423 | Ericsson |
| R3-202904 | Resource efficient PDCP duplication: enhancement 3 | Huawei, CMCC, Ericsson |
| R3-202905 | Introduction of NR_IIOT support to TS 38.463 | ZTE |
| R3-202906 | Introduction of NR_IIOT support to TS 38.473 | Huawei |
| 17.2.1 | PDCP Duplication for CA-only and for NR DC with CA | |
| R3-201662 | On the use of the additional tunnels and their implementation | Nokia, Nokia Shanghai Bell |
| R3-201663 | (TP for NR_IIoT BL CR for TS 38.423): Correction of the use of the additional tunnels | Nokia, Nokia Shanghai Bell |
| R3-201697 | (TP for Introduction of NR_IIOT support to TS 38.423) Clarification on primary LCID for split bearer operation | ZTE |
| R3-201698 | (TP for Introduction of NR_IIOT support to TS 38.473) Clarification on primary LCID for split bearer operation | ZTE |
| R3-202143 | Correction of BL CR related to the PDCP Duplication for more than copies | Ericsson |
| R3-202144 | Resolve FFS related to the PDCP Duplication | Ericsson |
| R3-202145 | Resolve FFS related to the PDCP Duplication | Ericsson |
| R3-202321 | (TP for NR_IIOT BL CR for TS 38.423): PDCP duplication with more than 2 entities | Huawei |
| R3-202322 | (TP for NR_IIOT BL CR for TS 38.463): PDCP duplication with more than 2 entities | Huawei |
| R3-202323 | (TP for NR_IIOT BL CR for TS 38.473): PDCP duplication with more than 2 entities | Huawei |
| R3-202520 | CB: # NRIIOT2_Email_NRIIoT_PDCPdup_morethan2 | ZTE - Moderator |
| R3-202620 | (TP for NR_IIoT BL CR for TS 38.423): Correction of the use of the additional tunnels | Nokia, Nokia Shanghai Bell |
| R3-202621 | Correction of BL CR related to the PDCP Duplication for more than copies | Ericsson |
| R3-202622 | (TP for Introduction of NR_IIOT support to TS 38.473) Clarification on primary LCID for split bearer operation | ZTE |
| R3-202697 | (TP for NR_IIoT BL CR for TS 38.423): Correction of the use of the additional tunnels | Nokia, Nokia Shanghai Bell |
| R3-202794 | Correction of BL CR related to the PDCP Duplication for more than copies | Ericsson |
| 17.2.2 | Dynamic Control | |
| R3-201664 | Coordination of UL and DL transmission for multiplication over up to 4 RLCs | Nokia, Nokia Shanghai Bell |
| R3-201665 | (TPs for NR_IIoT BL CRs for TS 38.423): Enabling coordination for DL and UL multiplication over up to 4 RLCs | Nokia, Nokia Shanghai Bell |
| R3-201666 | (TPs for NR_IIoT BL CRs for TS 38.425): Enabling assistance information for DL coordination of the multiplication over up to 4 RLCs | Nokia, Nokia Shanghai Bell |
| R3-201667 | Response LS on Network Coordination for UL PDCP Duplication | Nokia, Nokia Shanghai Bell |
| R3-201699 | (TP for Introduction of NR_IIOT support to TS 38.423) PDCP duplication coordination | ZTE |
| R3-201700 | (TP for Introduction of NR_IIOT support to TS 38.473) PDCP duplication coordination | ZTE |
| R3-201701 | (TP for Introduction of NR_IIOT support to TS 38.463) PDCP duplication coordination | ZTE |
| R3-201702 | (TP for Introduction of NR_IIOT support to TS 38.425) PDCP duplication coordination | ZTE |
| R3-201952 | Discussion on Dynamic control of PDCP Duplication | CATT |
| R3-201953 | (TP for [NR_IIOT] BL CR for TS 38.425)Discussion on Dynamic control of PDCP Duplication | CATT |
| R3-202324 | (TP for NR_IIOT BL CR for TS 38.425): Assistance information for DL PDCP duplication with more than 2 entities | Huawei, CMCC |
| R3-202325 | (TP for NR_IIOT BL CR for TS 38.425): Dynamic control of UL duplication- activation suggestion | Huawei |
| R3-202326 | (TP for NR_IIOT BL CR for TS 38.425): Dynamic control of UL duplication - assistance information | Huawei |
| R3-202327 | [DRAFT] Reply LS on coordination for UL duplication | Huawei |
| R3-202437 | Dynamic control of PDCP duplication | China Mobile International Ltd |
| R3-202521 | CB: # NRIIOT3_Email_NRIIoT_PDCPdup_ctrl | CATT - Moderator |
| R3-202703 | CB: # NRIIOT3_Email_NRIIoT_PDCPdup_ctrl | CATT - Moderator |
| R3-202735 | (TP for NR_IIOT BL CR for TS 38.425): Assistance information for DL PDCP duplication with more than 2 entities | Huawei, CMCC, CATT |
| 17.2.3 | Enhancements for More Efficient DL PDCP Duplication | |
| R3-201668 | Even more simplified solution to make duplication actually more efficient | Nokia, Nokia Shanghai Bell |
| R3-201669 | (TP for NR_IIoT BL CR for TS 38.425): Increasing duplication efficiency by avoiding unnecessary duplication | Nokia, Nokia Shanghai Bell |
| R3-201703 | TP for enhancement1 for more efficient PDCP duplication to TS38.425 | ZTE |
| R3-202146 | Further discussion on Enhancements for More Efficient DL PDCP Duplication | Ericsson |
| R3-202147 | Enhancement on Resource efficient PDCP duplication, enh 3 | Ericsson |
| R3-202328 | Resource efficient PDCP duplication | Huawei |
| R3-202522 | CB: # NRIIOT4_Email_NRIIoT_PDCPdup_enh | Ericsson - Moderator |
| R3-202704 | CB: # NRIIOT4_Email_NRIIoT_PDCPdup_enh | Ericsson - Moderator |
| R3-202760 | Enhancement on Resource efficient PDCP duplication, enh 3 | Ericsson |
| 17.2.4.1 | Common (Stage 2) | |
| R3-202329 | Higher layer duplication for TS 37.340 | Huawei |
| R3-202523 | CB: # NRIIOT5_Email_NRIIoT_HLmulticonn_st2 | Huawei - Moderator |
| 17.2.4.2 | Solution #1 | |
| R3-201704 | (TP for Introduction of NR_IIOT support to TS38.413): Redundant PDU session establishment | ZTE |
| R3-201705 | (TP for Introduction of NR_IIOT support to TS38.423): Redundant PDU session establishment | ZTE |
| R3-201706 | (TP for Introduction of NR_IIOT support to TS38.463): Redundant PDU session establishment | ZTE |
| R3-201954 | Remaining issues of the Solution#1 | CATT |
| R3-201955 | (TP for [NR_IIOT] BL CR for TS 38.413)Remaining issues of the Solution#1 | CATT |
| R3-201956 | (TP for [NR_IIOT] BL CR for TS 38.423)Remaining issues of the Solution#1 | CATT |
| R3-201957 | (TP for [NR_IIOT] BL CR for TS 38.463)Remaining issues of the Solution#1 | CATT |
| R3-202073 | (TP for NR_IIOT BL CR for TS 38.413) Redundant PDU session setup | Samsung |
| R3-202148 | Discussions on remaining issues related to Sol 1 for Higher Layer Multi-Connectivity | Ericsson |
| R3-202149 | Include the used RSN in the response | Ericsson |
| R3-202150 | Include the used RSN in the response | Ericsson |
| R3-202151 | Introducing the Used RSN to E1AP | Ericsson |
| R3-202152 | Introducing RSN Information to E1AP | Ericsson |
| R3-202276 | Discussion on open issues for Solution #1 | LG Electronics |
| R3-202277 | (TP for NR_IIOT BL CR for TS 38.413): Introduction of Redundant Transmission Information for Solution #1 | LG Electronics |
| R3-202278 | (TP for NR_IIOT BL CR for TS 38.463): Introduction of Redundant Transmission Information for Solution #1 | LG Electronics |
| R3-202330 | (TP for NR_IIOT BL CR for TS 38.473): Higher layer duplication for solution 1 | Huawei |
| R3-202331 | (TP for NR_IIOT BL CR for TS 38.463): Higher layer duplication for solution 1 | Huawei |
| R3-202524 | CB: # NRIIOT6_Email_NRIIoT_HLmulticonn_sol1 | ZTE - Moderator |
| R3-202623 | (TP for [NR_IIOT] BL CR for TS 38.413)Remaining issues of the Solution#1 | CATT |
| R3-202624 | Include the used RSN in the response | Ericsson |
| R3-202625 | (TP for Introduction of NR_IIOT support to TS38.463): Redundant PDU session establishment | ZTE |
| R3-202705 | (TP for [NR_IIOT] BL CR for TS 38.413)Remaining issues of the Solution#1 | CATT |
| R3-202706 | Include the used RSN in the response | Ericsson |
| R3-202707 | CB: # NRIIOT6_Email_NRIIoT_HLmulticonn_sol1 | ZTE - Moderator |
| R3-202795 | Include the used RSN in the response | Ericsson |
| 17.2.4.3 | Solution #4 | |
| R3-201821 | (TP for BL CR NR IIoT for 38.413) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-201822 | (TP for BL CR NR IIoT for 38.423) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-201823 | (TP for BL CR NR IIoT for 38.463) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-202525 | CB: # NRIIOT7_Email_NRIIoT_HLmulticonn_sol4 | Nokia - Moderator |
| R3-202582 | (TP for BL CR NR IIoT for 38.413) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-202583 | (TP for BL CR NR IIoT for 38.423) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| R3-202584 | (TP for BL CR NR IIoT for 38.463) Correction of redundant tunnels | Nokia, Nokia Shanghai Bell |
| 17.3.2 | TSC Assistance Information | |
| R3-202332 | (TP for NR_IIoT BL CR for TS 38.300) : Introduction of CN PDB and TSC parameters | Huawei |
| R3-202526 | CB: # NRIIOT8_Email_NRIIoT_TSC_assist_info | Huawei - Moderator |
| R3-202655 | (TP for NR_IIoT BL CR for TS 38.300) : Introduction of CN PDB and TSC parameters | Huawei |
| 17.3.3 | Time Reference Information | |
| R3-202153 | Correction related to the Reference Time reporting | Ericsson |
| R3-202333 | (TP for NR_IIOT BL CR for TS 38.473): Reference timing information | Huawei |
| R3-202527 | CB: # NRIIOT9_Email_NRIIoT_time_ref_info | Ericsson - Moderator |
| 17.4 | Ethernet Type Bearer Signaling in NG-RAN | |
| R3-201548 | Support of Ethernet Header Compression | Huawei, Samsung, CMCC |
| R3-201549 | Support of Ethernet Header Compression | Huawei |
| R3-201552 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-201553 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-201673 | TP to Ethernet BLCR 38.463 on EHC parameters | Huawei, CMCC |
| R3-201674 | (TP to BL CR#1691 “Support of Ethernet Type Bearer” for TS36.413) Update of non IP Type to Ethernet Type | Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-201675 | (TP to BL CR#1340 “Support of Ethernet Type Bearer” for TS36.423) Update of non IP Type to Ethernet Type | Huawei, Nokia, Nokia Shanghai Bell, CMCC |
| R3-201734 | TP to Ethernet BL CR 38.463 on support RoCH and EHC | Huawei, Vodafone |
| R3-202169 | Support of Ethernet type | Nokia, Nokia Shanghai Bell |
| R3-202170 | (TP for baseline CR on Ethernet for TS 38.463) Correction of Ethernet type | Nokia, Nokia Shanghai Bell |
| R3-202171 | (TP for baseline CR on Ethernet for TS 38.413) Correction of ethernet type | Nokia, Nokia Shanghai Bell |
| R3-202528 | CB: # NRIIOT10_Email_Ethernet_Type_Bearer_Signaling | Nokia - Moderator |
| R3-202644 | (TP for baseline CR on Ethernet for TS 38.413) Correction of ethernet type | Nokia, Nokia Shanghai Bell |
| R3-202662 | TP to Ethernet BLCR 38.463 on EHC parameters | Huawei, CMCC |
| R3-202899 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-202900 | Support of Ethernet Type Bearer | Huawei, Vodafone, Nokia |
| R3-202927 | Support of Ethernet Header Compression | Huawei, Samsung, CMCC |
| R3-202928 | Support of Ethernet Header Compression | Huawei |
| 18.1 | General | |
| R3-201562 | Signalling UE capability Identity | Huawei, Samsung Electronics, CATT, Ericsson, Qualcomm |
| R3-201563 | X2AP support for Radio Capability Signaling Optimization | Samsung, CATT, Ericsson, Huawei, Qualcomm |
| R3-201564 | Supporting of RACS in XnAP | CATT, Samsung, Huawei, Ericsson, Qualcomm |
| R3-201573 | Introducing Radio Capability Optimisation (RACS) | Ericsson, Qualcomm, CATT, Samsung, Huawei |
| R3-201884 | Work plan for RACS-RAN work item | CATT, MediaTek Inc. |
| R3-202529 | CB: # 38_Email_RACS_general | CATT - Moderator |
| R3-202922 | Signalling UE capability Identity | Huawei, Samsung Electronics, CATT, Ericsson, Qualcomm |
| R3-202923 | X2AP support for Radio Capability Signaling Optimization | Samsung, CATT, Ericsson, Huawei, Qualcomm |
| R3-202924 | Introducing Radio Capability Optimisation (RACS) | Ericsson, Qualcomm, CATT, Samsung, Huawei |
| R3-202925 | Supporting of RACS in XnAP | CATT, Samsung, Huawei, Ericsson, Qualcomm |
| 18.2 | Open Items | |
| R3-201639 | TP for NR_RACS BL CR for TS 38.423 Some XnAP Corrections with NGAP Alignment | ZTE |
| R3-201641 | Further Discussion of RACS ID Usage in MR-DC Scenarios | ZTE |
| R3-201643 | TS37.340 Introduction of RACS Feature in MR-DC Rel-16 | ZTE |
| R3-201644 | TP for LTE_RACS BL CR for TS 36.413 Clarification of RACS Mapping Procedure | ZTE |
| R3-201645 | TP for NR_RACS BL CR for TS 38.413 Clarification of RACS Mapping Procedure | ZTE |
| R3-201768 | UE Radio Access Capability related ID and information | NEC |
| R3-201769 | (TP for RACS BL CR for TS 36.413) UE Radio Access Capability ID and information | NEC |
| R3-201770 | (TP for RACS BL CR for TS 36.423) UE Radio Access Capability ID and information | NEC |
| R3-201771 | (TP for RACS BL CR for TS 38.413) UE Radio Access Capability ID and information | NEC |
| R3-201772 | (TP for RACS BL CR for TS 38.423) UE Radio Access Capability ID and information | NEC |
| R3-201806 | (TP for 38.413 CR#0347 RACS) Further discussion of open issues in RACS | Qualcomm Incorporated |
| R3-201885 | Discussion on left issues for RACS | CATT |
| R3-201886 | (TP for NR BL CR for TS 36.413) Introduction of UE Radio Capability ID for UE Radio Capability Match | CATT |
| R3-201887 | (TP for NR BL CR for TS 38.413) Introduction of UE Radio Capability ID for UE Radio Capability Check | CATT |
| R3-201888 | (TP for NR BL CR for TS 36.423) Introduction of UE Radio Capability ID for LTE-DC | CATT |
| R3-201889 | LS on RACS capability exchange | CATT |
| R3-202004 | Open issues for RACS support in Dual Connectivity | Samsung |
| R3-202005 | (TP for RACS for TS 36.423) RACS support in Dual Connectivity | Samsung |
| R3-202006 | (TP for RACS for TS 38.423) RACS support in Dual Connectivity | Samsung |
| R3-202154 | [TP for BL CR NGAP] Removing open issues on RACS | Ericsson |
| R3-202155 | [TP for BL CR S1AP] Removing open Issues on RACS | Ericsson |
| R3-202156 | [TP for BL CR X2AP] Removing open issues on RACS | Ericsson |
| R3-202157 | [TP for BL CR XnAP] Removing open issues on RACS | Ericsson |
| R3-202158 | Open topics for Rel-16 UE Radio Capability Optimizations WI | Ericsson |
| R3-202247 | Signalling UE capability Identity | Huawei |
| R3-202248 | (TP for RACS BL CR for TS 36.413): Signalling UE capability Identity | Huawei |
| R3-202249 | (TP for RACS BL CR for TS 36.423): Signalling UE capability Identity | Huawei |
| R3-202250 | (TP for RACS BL CR for TS 38.413): Signalling UE capability Identity | Huawei |
| R3-202251 | (TP for RACS BL CR for TS 38.423): Signalling UE capability Identity | Huawei |
| R3-202458 | Response to R3-201885 | Nokia, Nokia Shanghai Bell |
| R3-202530 | CB: # 39_Email_RACS_common_issues | Ericsson - Moderator |
| R3-202531 | CB: # 42_Email_RACS_S1_NG_issues | Huawei - Moderator |
| R3-202532 | CB: # 43_Email_RACS_X2_Xn_issues | Samsung - Moderator |
| R3-202533 | CB: # 44_Email_RACS_st2 | ZTE - Moderator |
| R3-202576 | TS37.340 Introduction of RACS Feature in MR-DC Rel-16 | ZTE |
| R3-202658 | (TP for 38.413 CR#0347 RACS) Further discussion of open issues in RACS | Qualcomm Incorporated |
| R3-202669 | (TP for RACS BL CR for TS 36.413): Signalling UE capability Identity | Huawei |
| R3-202683 | Signalling UE capability Identity | Huawei |
| R3-202693 | Introducing Radio Capability Optimisation (RACS) | Nokia, Nokia Shanghai Bell |
| R3-202731 | [TP for BL CR X2AP] Removing open issues on RACS | Ericsson, Samsung |
| R3-202732 | [TP for BL CR XnAP] Removing open issues on RACS | Ericsson, Samsung |
| 19.1 | General | |
| R3-201547 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| R3-201605 | Running CR for the introduction of NR positioning | Ericsson |
| R3-201606 | Introduction of NR Positioning in NRPPa | Ericsson, Intel |
| R3-201607 | Positioning support over F1AP | Huawei |
| R3-201749 | Running CR for the introduction of NR positioning | Ericsson |
| R3-202046 | (TP to BL CR for TS 38.305) Update on NG-RAN architecture | Huawei |
| R3-202047 | (TP to BL CR for TS 38.455) Measurement ID clean-up | Huawei |
| R3-202048 | Positioning Support over F1AP CR | Huawei |
| R3-202049 | (TP to BL CR for TS 38.305) Clean up related CU-DU | Huawei |
| R3-202534 | CB: # 45_Email_Pos_BLs_arch | Intel - Moderator |
| R3-202776 | (TP to BL CR for TS 38.455) Measurement ID clean-up | Huawei |
| R3-202911 | Introduction of NR Positioning in NRPPa | Ericsson, Intel |
| R3-202912 | Positioning support over F1AP | Huawei |
| R3-202913 | Introduction of positioning support over F1AP | Qualcomm Incorporated |
| 19.2.1 | NRPPa Impacts | |
| R3-201630 | (TP for NR_POS BL CR for TS 38.305) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell |
| R3-201631 | (TP for NR_POS BL CR for TS 38.455) Further details for RAT dependent positioning | Nokia, Nokia Shanghai Bell |
| R3-201681 | On TRP selection | Intel Corporation |
| R3-201893 | E-CID measurement support in NRPPa | NTT DOCOMO INC. |
| R3-202050 | (TP to BL CR for TS 38.455) Open issues related to TRP information exchange | Huawei |
| R3-202051 | (TP to BL CR for TS 38.455) Beam pattern report for DL-AOD | Huawei |
| R3-202052 | (TP to BL CR for TS 38.455) NR E-CID measuremnt procedure | Huawei |
| R3-202192 | (TP to NRPPa BL CR 38.455): discussion on remaining issues of NRPPa | Ericsson |
| R3-202206 | (TP for NR_POS BL CR for TS 38.455) NRPPa Enhancement to support TRP Information Transfer for Selected TRPs | Qualcomm Incorporated |
| R3-202535 | CB: # 46_Email_Pos_TRPs | Intel - Moderator |
| R3-202536 | CB: # 47_Email_Pos_NR_E-CID | Nokia - Moderator |
| R3-202537 | CB: # 48_Email_Pos_NR_barTBS | Polaris Wireless - Moderator |
| R3-202645 | (TP for NR_POS BL CR for TS 38.305) Support for UL NR E-CID | Nokia, Nokia Shanghai Bell |
| R3-202646 | LS on support for UL NR E-CID | Nokia, Nokia Shanghai Bell |
| R3-202872 | (TP to BL CR for 38.455) Introduction of TRP support in NRPPa | Intel |
| R3-202933 | Support for UL NR E-CID | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm |
| 19.2.2 | DL PRS Exchange over Xn | |
| R3-202053 | Discussion on spatial relationship of DL and UL resources | Huawei |
| R3-202193 | On the benefits of exchanging DL PRS configuration over Xn | Ericsson |
| R3-202538 | CB: # 49_Email_Pos_PRS_exchange_Xn | Ericsson - Moderator |
| 19.3 | Transmission Measurement Function | |
| R3-202054 | (TP for BL CR for TS 38.455) Measurement procedure related issues | Huawei |
| R3-202205 | (TP for NR_POS BL CR for TS 38.305) Split Architecture support of TRPs | Qualcomm Incorporated |
| 19.4 | Broadcast Assistance Data Delivery | |
| R3-201807 | (TP for NR_POS BL CR for TS 38.455) NRPPa open issues for Broadcast Assistance Data Delivery | Qualcomm Incorporated |
| R3-201808 | (TP for NR_POS BL CR for TS 38.473) F1AP issues for Broadcast Assistance Data Delivery | Qualcomm Incorporated |
| R3-201958 | Introduce Positioning SI Area ID | CATT |
| R3-201959 | (TP for [NR_POS-Core] BL CR for TS 38.455) Introduce Positioning SI Area ID | CATT |
| R3-202055 | (TP to BL CR for TS 38.455) NR Assistance Data Delivery | Huawei |
| R3-202194 | Discussion on remaining issues of delivery of Positioning Assistance Data | Ericsson |
| R3-202195 | (TP to F1AP BL CR): Addressing remaining issues of delivery of Positioning Assistance Data over F1AP | Ericsson |
| R3-202539 | CB: # 50_EmaIl_Pos_Broadcast_assist_data | Huawei - Moderator |
| R3-202698 | (TP for NR_POS BL CR for TS 38.473) Removal of FFS on use of octet string in Broadcast Assistance Data Delivery procedures | Qualcomm |
| R3-202749 | LS on support for Area Scope in Assistance Information metadata | Ericsson |
| R3-202755 | (TP for NR_POS BL CR for TS 38.455) NRPPa open issues for Broadcast Assistance Data Delivery | Qualcomm Incorporated |
| 19.5 | Positioning Support in split gNB Architecture | |
| R3-201682 | Alignment between NRPPa and F1 | Intel Corporation |
| R3-202056 | (TP to BL CR for TS 38.470) F1 support for NR positioning | Huawei |
| R3-202057 | (TP for BL CR for TS 38.473) F1 support for NR positioning | Huawei |
| R3-202196 | (TP to F1AP BL CR 38.473): Signalling for Aperiodic Positioning of SRS configuration | Ericsson |
| R3-202197 | (TP to TS 38.305): support of positioning over F1AP | Ericsson |
| R3-202540 | CB: # 51_Email_Pos_split_arch | Ericsson - Moderator |
| R3-202777 | (TP to BL CR for TS 38.470) F1 support for NR positioning | Huawei |
| R3-202778 | (TP for BL CR for TS 38.473) Introduction of TRP information exchange procedure | Huawei |
| R3-202793 | (TP for BL CR for TS 38.473) Alignment between NRPPa and F1 | Intel Corporation, Huawei |
| 19.6 | Others | |
| R3-201694 | (TP to BL CR#0008r12 "Introduction of NR Positioning in NRPPa" for TS38.455) Addition of broadcast of barometric pressure and TBS assistance data | Polaris Wireless, NextNav, AT&T, FirstNet, Intel |
| 20.1 | General | |
| R3-201570 | Support of NR V2X SIB in gNB-DU | Ericsson |
| R3-201575 | Support of NR V2X over S1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-201576 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics |
| R3-201577 | Support of NR V2X over NG | LG Electronics, Ericsson, Huawei, CATT |
| R3-201578 | Support of NR V2X over Xn | Ericsson, LG Electronics, CATT, Huawei |
| R3-201579 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-202541 | CB: # 1012_Email_V2X_BLs | LG - Moderator |
| R3-202571 | Support of NR V2X SIB in gNB-DU | Ericsson |
| R3-202572 | Support of NR V2X over Xn | Ericsson, LG Electronics, CATT, Huawei |
| R3-202665 | Support of NR V2X over S1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-202666 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| R3-202670 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics |
| R3-202686 | Support of NR V2X over NG | LG Electronics, Ericsson, Huawei, CATT |
| R3-202787 | Support of NR V2X SIB in gNB-DU | Ericsson |
| R3-202873 | Support of NR V2X over X2 | CATT, Huawei, Ericsson, LG Electronics |
| R3-202874 | Support of NR V2X over Xn | Ericsson, LG Electronics, CATT, Huawei |
| R3-202875 | Support of NR V2X over F1 | Huawei, LG Electronics, Ericsson, CATT |
| 20.2.2 | V2X Support over F1 | |
| R3-201640 | Remaining issues on F1 support for 5G sidelink resource modes | LG Electronics |
| R3-201649 | (TP for BLCR 38.473) remaining Issues on F1 | LG Electronics |
| R3-201748 | [DRAFT] Reply LS on Sidelink UE Information | LG Electronics |
| R3-201882 | Further consideration on PC5 QoS Parameters over F1 | CATT |
| R3-201883 | (TP for NR BL CR for TS 38.473) PC5 QoS Parameters over F1 | CATT |
| R3-202037 | Discussion on remaining issues on F1 | ZTE, Sanechips |
| R3-202058 | (TP for V2X BL CR for TS 38.473): Remaining issues on F1 | ZTE, Sanechips |
| R3-202198 | Discussion on support of SL UE information over F1 | Ericsson |
| R3-202199 | Clarification on SL DRB QoS | Ericsson |
| R3-202228 | (TP for V2X BL CR for 38.473) F1 impacts for V2X | Huawei |
| R3-202426 | [DRAFT] LS on F1 impact on NR V2X | Huawei |
| R3-202542 | CB: # 1013_Email_V2X_F1 | Huawei - Moderator |
| R3-202677 | (TP for V2X BL CR for 38.473) F1 impacts for V2X | Huawei |
| R3-202831 | Reply LS to RAN2 on Sidelink UE Information | LG Electronics |
| 20.2.3 | Resource Coordination between NG-RAN Nodes for V2X Sidelink | |
| R3-202200 | Removal of exchanging V2X configuration between NG-RAN nodes | Ericsson |
| R3-202201 | (TP to V2X BL CR for TS 36.423 and 38.473): Removal of exchanging V2X configuration between NG-RAN nodes | Ericsson |
| R3-202229 | (TP for V2X for TS 36.423) Remove FFS for V2X configuration exchange | Huawei |
| R3-202230 | (TP for V2X BL CR for TS 38.423 & 38.473) Remove FFS for V2X configuration exchange | Huawei |
| R3-202543 | CB: # 1014_Email_V2X_ResCoord | Ericsson - Moderator |
| R3-202774 | (TP to V2X BL CR for TS 36.423): Removal of exchanging V2X configuration between NG-RAN nodes | Ericsson |
| R3-202775 | (TP to V2X BL CR for TS 38.473): Removal of exchanging V2X configuration between NG-RAN nodes | Ericsson |
| 20.2.4 | Support for QoS | |
| R3-201642 | Issue on PC5 QoS parameters | LG Electronics |
| R3-201680 | On alternative QoS profiles | Intel Corporation |
| R3-201733 | (TP for BLCR 38.473) on PC5 QoS parameters | LG Electronics |
| R3-202172 | Support for alternative QoS profiles | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics |
| R3-202183 | (TP for BL CR V2X for 38.413) Support for alternative QoS profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics |
| R3-202202 | (TP to V2X BL CR for TS 38.423): Support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics |
| R3-202203 | (TP to V2X BL CR for TS 38.473): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics |
| R3-202204 | Reply LS on Enhancements to QoS Handling for V2X communication over Uu reference point | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics |
| R3-202231 | Discusssion on Alternative QoS Profiles | Huawei, Vodafone |
| R3-202232 | Support of Alternative QoS Profiles | Huawei, Vodafone |
| R3-202233 | Support of Alternative QoS Profiles | Huawei, Vodafone |
| R3-202234 | Support of Alternative QoS Profiles | Huawei, Vodafone |
| R3-202334 | Support of alternative QoS profiles for V2X and handover into congested cells | VODAFONE Group Plc |
| R3-202459 | Response to R3-202172, R3-202183, R3-202202 “Support for alternative QoS profiles” and related NG and Xn interface CRs | VODAFONE Group Plc |
| R3-202544 | CB: # 1015_Email_V2X_QoS | Nokia - Moderator |
| R3-202708 | [DRAFT] LS on clarification of the parameters within Alternative QoS Profiles | Huawei |
| R3-202771 | (TP to V2X BL CR for TS 38.423): Support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics |
| R3-202772 | (TP to V2X BL CR for TS 38.473): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics |
| R3-202773 | (TP for BL CR V2X for 38.413) Support for alternative QoS profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics |
| R3-202834 | CB: # 1015_Email_V2X_QoS | Nokia - Moderator |
| R3-202846 | CB: # 1015_Email_V2X_QoS | Nokia - Moderator |
| R3-202847 | (TP for BL CR V2X for 38.413) Support for alternative QoS profiles over NG | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics |
| R3-202848 | (TP to V2X BL CR for TS 38.423): Support of Alternative QoS profiles over Xn | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics |
| R3-202849 | (TP to V2X BL CR for TS 38.473): Support of Alternative QoS profiles over F1 | Ericsson, Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, LG Electronics |
| R3-202856 | LS on Stage 3 for V2X QoS | Nokia, Huawei |
| 21.1 | General | |
| R3-201580 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| R3-201581 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| R3-201967 | Updated work plan for WWC | Huawei (Rapporteur) |
| R3-202545 | CB: # 40_Email_WWC_general | Huawei - Moderator |
| R3-202876 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| R3-202877 | CR for introducing WWC in RAN | Huawei, Telecom Italia, BT, Broadcom |
| 21.2 | NG Support for WWC | |
| R3-201968 | (TP for WWC BL CR for TS 29.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, BT, Broadcom |
| R3-201969 | (TP for WWC BL CR for TS 38.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, BT, Broadcom |
| R3-201970 | (TP for WWC BL CR for TS 29.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, BT, Broadcom |
| R3-201971 | (TP for WWC BL CR for TS 38.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, BT, Broadcom |
| R3-202159 | [TP for BL CR NGAP] Selected PLMN ID in Initial UE Message for | Ericsson |
| R3-202160 | [TP for BL CR NGAP] How to introduce a new Choice branch in tabular | Ericsson |
| R3-202546 | CB: # 41_Email_WWC_st3 | Huawei - Moderator |
| R3-202727 | (TP for WWC BL CR for TS 29.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, BT, Broadcom, Telecom Italia |
| R3-202728 | (TP for WWC BL CR for TS 38.413): Support for interfacing Trusted non-3GPP Access Networks to the 5GC | Huawei, BT, Broadcom, Telecom Italia |
| R3-202729 | (TP for WWC BL CR for TS 29.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, BT, Broadcom, Telecom Italia |
| R3-202730 | (TP for WWC BL CR for TS 38.413): Support for interfacing Wireline 5G Access Networks to the 5GC | Huawei, BT, Broadcom, Telecom Italia |
| 30 | Other WIs/SIs Impacting RAN3 | |
| R3-201661 | Support for MCG RLF information delivery over SRB3 | Nokia, Nokia Shanghai Bell, Huawei, NEC |
| 31.3 | NR | |
| R3-201767 | Correction of the criticality of the TNLA to add/update/remove list | NEC |
| 31.3.1 | Resource Coordination Over F1 | |
| R3-202235 | Correction on resource coordination over F1 | Huawei |
| 31.3.3 | Direct Data Forwarding Between NG-RAN and E-UTRAN | |
| R3-201646 | TS38.423 Support of Intra-System Direct DF with Shared Source NG-RAN Node | ZTE, CATT, China Telecom |
| R3-201647 | TS36.413 Correction of 1217 from NG-RAN node to gNB | ZTE |
| R3-201648 | TS38.413 Correction of 1227 from NG-RAN node to gNB | ZTE |
| R3-201695 | Support of direct data forwarding for inter-system HO | China Telecom, CATT,Nokia , Nokia Shanghai Bell |
| R3-201824 | Support of direct data forwarding for inter-system Handover | Nokia, Nokia Shanghai Bell, CATT, China Telecom |
| R3-201825 | Correction of inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom, Huawei |
| R3-201826 | Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom, Huawei |
| R3-202003 | Discussion on E1AP for inter-system direct data forwarding | CATT, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-202074 | SA to EN DC direct forwarding with shared SgNB/gNB | Samsung, Nokia, Nokia Shanghai Bell, CATT, China Telecom, Huawei |
| R3-202080 | Support of inter-node handover with a shared split (S)gNB | CATT, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-202161 | Inter-system handover involving EN-DC supporting direct forwarding with shared SgNB/gNB | Ericsson |
| R3-202768 | Summary of offline discussion on Direct forwarding Inter system HO involving DC | Nokia - Moderator |
| R3-202769 | Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom, Huawei |
| R3-202800 | Summary of offline discussion on Direct forwarding Inter system HO involving DC | Nokia - Moderator |
| R3-202801 | Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell, CATT, Samsung, China Telecom, Huawei |
| 31.3.4.1 | Other Rel-16 Corrections | |
| R3-201650 | TS37.340 Stage2 Refined Descriptions of SCG Suspend&Resume Operation | ZTE |
| R3-201651 | TS36.423 Corrections of SCG Suspend&Release Behaviors with EN-DC in Rel-16 | ZTE |
| R3-201788 | Full slot format support | Qualcomm Incorporated |
| R3-201789 | Full slot formats support in Intended TDD UL-DL Configuration | Qualcomm Incorporated |
| R3-201827 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, TMO |
| R3-201828 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, TMO |
| R3-201829 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, TMO |
| R3-201830 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, TMO |
| R3-201831 | Correction of S-NSSAI range | Nokia, Nokia Shanghai Bell, AT&T, TMO |
| R3-201851 | SRS-RSRP configuration for CLI | Nokia, Nokia Shanghai Bell, China Telecom, Orange, LGE, ZTE |
| R3-201904 | Discussion on One PDU session with Multiple CU-UPs | ZTE Corporation |
| R3-201905 | Support one PDU session with multiple CU-UPs for TS38.401 | ZTE Corporation |
| R3-201907 | Support one PDU session with multiple CU-UPs for TS38.413 | ZTE Corporation |
| R3-201972 | Clarification of Security Result | Huawei |
| R3-202039 | On the challenges of TNL address discovery with the flexible NG-RAN Node ID length | Ericsson, Verizon |
| R3-202040 | Draft LS on broadcasting gNB ID length in system information block | Ericsson, Verizon |
| R3-202041 | gNB-CU-UP ID | Ericsson |
| R3-202236 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-202237 | Further correction on fast MCG recovery via SRB3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-202238 | Correction to node name format | Ericsson, Verizon, Samsung |
| R3-202239 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung |
| R3-202240 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung |
| R3-202241 | Corrections to node name type | Ericsson, Verizon Wireless, Samsung |
| R3-202242 | Correction to SCG Resuming from suspension | Google Inc. |
| R3-202254 | Corrections of procedures for PWS tests | Ericsson, One2many |
| R3-202255 | Draft LS on Test Procedures for PWS | Ericsson, One2many |
| R3-202275 | CR 36.423 Correction to E-UTRA-NR Cell-level Resource Coordination | Ericsson, Deutsche Telekom |
| R3-202312 | Completion of RAN UE ID | Ericsson |
| R3-202313 | Completion of RAN UE ID | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-202314 | RAN UE ID for X2 | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-202315 | RAN UE ID for Xn | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-202316 | RAN UE ID for NG | Ericsson, Telecom Italia, Deutsche Telekom, Orange |
| R3-202320 | SRS-RSRP configuration for CLI | LGE, China Telecom, Orange, Nokia, Nokia Shanghai Bell, ZTE |
| R3-202359 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-202360 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT, Orange |
| R3-202378 | On X2 support for UE CLI measurement for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-202384 | Correction of CLI | ZTE, Ericsson, LGE |
| R3-202385 | SRS-RSRP configuration for CLI | ZTE, Nokia, Nokia Shanghai Bell, CMCC, LGE, China Telecom, Orange, China Unicom |
| R3-202386 | AMF Region Information in Xn setup procedure | ZTE, China Telecom,China Unicom |
| R3-202387 | AMF Region Information IE CR for Rel-15 38423 | ZTE, China Telecom,China Unicom |
| R3-202388 | AMF Region Information IE CR for Rel-16 38423 | ZTE, China Telecom,China Unicom |
| R3-202389 | RAN UE ID IE CR for Rel-16 38473 | ZTE, China Telecom,China Unicom |
| R3-202390 | RAN UE ID IE CR for Rel-15 38473 | ZTE, China Telecom,China Unicom |
| R3-202417 | Miscellaneous corrections to 37.473 | Huawei, China Unicom, Orange, TIM |
| R3-202418 | Miscellaneous corrections to 37.470 | Huawei, China Unicom, Orange, TIM |
| R3-202420 | Discussion on Extending Usage of RAN UE ID | Nokia, Nokia Shanghai Bell |
| R3-202770 | Summary of offline discussion on RAN UE ID | Nokia |
| 31.3.4.2 | Other TEI16 | |
| R3-201652 | TS38.300 Introduction of CSI-RS Based Measurement and Mobility for HO | ZTE, China Telecom |
| R3-201785 | Voice fallback triggered by PDU session resource setup | Qualcomm Incorporated |
| R3-201786 | Voice fallback triggered by PDU session resource setup (CR to 38.413) | Qualcomm Incorporated |
| R3-201787 | Direct data forwarding from source node to target SgNB in NR SA to EN-DC inter-system handover | Qualcomm Incorporated |
| R3-202042 | Addition of Local NG-RAN Node Identifier. | Ericsson |
| R3-202043 | Addition of Local NG-RAN Node Identifier to resolve NG-RAN ID from I-RNTI. | Ericsson |
| R3-202691 | TS38.300 Introduction of CSI-RS Based Measurement and Mobility for HO | ZTE, China Telecom |
| 31.4 | Rapporteur Corrections for Rel-16 | |
| R3-201690 | ASN.1 Correction of the Data Forwarding Response E-RAB List IE | Nokia, Ericsson |
| R3-201691 | NGAP Rapporteur corrections | Nokia |
| R3-201746 | Rapporteur: Corrections after implementation | Huawei |
| R3-202075 | Rapporteur's correction for TS 38.425 | Samsung |
| R3-202162 | Rapporteur’s Correction to XnAP version 16.1.0 | Ericsson |
| R3-202163 | Rapporteur’s Correction to X2AP version 16.1.0 | Ericsson |
| R3-202164 | Correctinos to Xn Setup message size limitation solution | Ericsson |
| R3-202165 | Wrong ASN.1 IE-Id for the New eNB UE X2AP ID Extension IE | Ericsson |
| R3-202376 | Rapporteur's editorial corrections for TS 38.463 | Ericsson |
| R3-202547 | CB: # 26_Email_Rel-16_Rapp_Corr | InterDigital - Moderator |